10
votes
Accepted
Naming conventions for component, event, helper parameters in Lightning Components?
The default values are component, event, and helper. It's in most (all?) of the documentation, and all of the default templates I've seen (e.g. when making a new controller). Some people shorten it to ...
8
votes
Accepted
Where does the colon (:) belong in the Apex SOQL query - to the operator or the variable?
: is the binding operator. It behaves differently depending on if you're using inline SOQL/SOSL or dynamic SOQL/SOSL.
With inline queries, : starts a section of Apex Code execution within the query. ...
5
votes
Where does the colon (:) belong in the Apex SOQL query - to the operator or the variable?
From a practical standpoint, either works. While SOQL does have some syntactically significant whitespace (e.g. between filters in the WHERE clause, between the last field in the SELECT clause and the ...
4
votes
Accepted
Does Capitalization in API Names Matter?
As a general rule, for XML- and JavaScript-based features, the API names are case-sensitive, and for JSON-, Apex-, and Visualforce-based features, it is case-insensitive, as well as basic features ...
3
votes
Does Capitalization in API Names Matter?
The Apex language is case-insensitive, but having a consistent casing pattern in your code base is a simple way to make your code easier to understand by people. The most significant convention is to ...
3
votes
Custom Labels - naming conventions - best practices?
Even though it depends on teams to teams when it comes around best practices, but as for your question
Any thoughts on what makes for good naming conventions for a pile of Custom Labels?
I have ...
3
votes
Why Salesforce naming conventions are like what they are?
Spaces are used as delimiters in both Apex and SOQL so this would not compile:
myObject.Personal Score__c = 5;
whereas this will:
myObject.Personal_Score__c = 5;
and if you want to, you can ...
2
votes
Custom Labels - naming conventions - best practices?
The most important part is consistency: don't name one label ERR_TOO_MANY_FILES and another VALUE_TOO_LONG_ERR. In my opinion, that's more important than trying to find the "one right way" (there isn'...
2
votes
Naming conventions for component, event, helper parameters in Lightning Components?
To be honest I would extremely advice against using single letters for the component/event/helper.
Single letter is a sign for local variable. Eg: i for iteration.
I agree that those 3 are ...
2
votes
Report Folder and Report Name Control (Validation? Workflow? Apex?)
Short answer is no, you can't do that. That being said, best practice is to NOT let users create folders. This practice is established for exactly the reason you mentioned.
As for reports. The report ...
2
votes
Accepted
Is it possible to use another name for the TestDataFactory class
TestDataFactory The name is just good as per the naming conventions. By giving this name does not make it special.
It does not count against code character count/coverage because you add @isTest to ...
2
votes
Why Salesforce naming conventions are like what they are?
The amount of space salesforce.com would save is literally nothing, as the object names are stored in a database that presumably uses a CHAR field type for the name, for performance reasons. This ...
2
votes
Where does the colon (:) belong in the Apex SOQL query - to the operator or the variable?
To the variable, because it is not part of the operator.
And I like to consider it as some sort of modifier/pointer to make that variable work with the query.
2
votes
Accepted
Best Practices - Changing Standard Object names
While I'm not an architect, and haven't seen nearly as many acquisitions (and have been on the acquiree side more often than not), one thing that I/my boss have used in evaluating more routine ...
1
vote
Accepted
fflib service layer naming convention
To quote Andrew Fawcett, page 163 Salesforce Lightning Platform Enterprise Architecture
The actual name of the service can be pretty much anything you like, typically a major module or a significant ...
1
vote
Custom Labels - naming conventions - best practices?
I like an adaptation of the naming convention from this blog:
"Define sensible categories for the labels. e.g. UI Button Label, UI
Text, UI Error Message etc.
Name = [Category with underscores]_[...
1
vote
Naming conventions for component, event, helper parameters in Lightning Components?
I only deal with lightning components now and found it much easier to always stick to component, event, helper in their full format. I find that shortening it obfuscates unnecessarily for new ...
1
vote
Accepted
Shortening IF formula for multiple variations of a Custom naming convention Field
I'm mobile, but it seems to me that the first four parts could read like this:
If(contains(parent.name, "client1"),
If(isblank(field1),
If(isblank(field2),
// field1 is blank, field2 is ...
1
vote
Shortening IF formula for multiple variations of a Custom naming convention Field
This is just a start, and not nearly a complete optimalisation. If statements 3, 4 and 5 have the same outcome, namely:
Show_Code__r.Name & "_" &
SUBSTITUTE(VenueCity__c," ","") & "_" &...
1
vote
Accepted
Deployment Naming Convention
The naming convention depends on your organization's development style. The most important part about using naming conventions is to have a naming convention. It doesn't really matter what it is, so ...
1
vote
Deployment Naming Convention
The naming convention depends more on the kind of project/work (administration/development) you do to do the migrations.
Administration
For administration works, we usually get change requests and a ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
naming-convention × 15apex × 3
bestpractice × 2
lightning-aura-components × 1
unit-test × 1
reporting × 1
formula × 1
deployment × 1
lookup × 1
custom-field × 1
validation × 1
administration × 1
standard-objects × 1
customlabel × 1
translation × 1
translation-workbench × 1
architecture × 1
describefieldresult × 1
business-logic × 1
data-model × 1
fflib × 1
framework × 1
automated-process × 1
test-data × 1
prettier × 1