Skip to content

Updated Apex Type Names tables #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updated Apex Type Names tables #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions _pages/Salesforce-Naming-Conventions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -481,14 +481,15 @@ The following are examples of Apex type naming that should not be used

Type Name | Reason
-----------|:------
map Contacts | "map", “id”, and “string” do not start with an uppercase letter.
String Contact | “string” does not start with an uppercase letter.
map Contacts | "map" does not start with an uppercase letter
string Contact | “string” does not start with an uppercase letter

The following are examples of the naming convention that will be used

Type Name | Reason
-----------|:------
Map Contacts | Starts with an uppercase letter String Contact Starts with an uppercase letter
Map Contacts | Starts with an uppercase letter
String Contact | Starts with an uppercase letter

____

Expand Down