Skip to content

Commit 062e8cf

Browse files
author
Charles S. Koppelman-Milstein
committed
more explicit about when in doubt
1 parent 7ea5df5 commit 062e8cf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Apex style guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ We follow the Java standard of capitalization with the listed exceptions. That
111111

112112
Native Apex methods and classes should generally be referenced as written in official Salesforce documentation. This means that schemas and classes are `UpperCamelCase` and methods are `lowerCamelCase`. The only deviation from this rule is `SObject` which should be written as such (in the documentation, it is usually written `sObject` which does not conform to this style guide and should not be used).
113113

114-
However, when referencing any metadata (SObject, SObjectField, FieldSet, Action, Class, Page, etc.), use the declared capitalization. When referencing a method, field, etc., that is not capitalized according to these rules, use the declared capitalization.
114+
However, when referencing any metadata (SObject, SObjectField, FieldSet, Action, Class, Page, etc.), use the declared capitalization. Even when referencing a method, field, etc., that is not capitalized according to these rules, still use the declared capitalization.
115115

116116
<a name="example"></a>
117117
### Example

0 commit comments

Comments
 (0)