This repository contains the complete definition of NimbleUser's coding standards for source code in the Apex Programming Language. An Apex source file is described as being in NimbleUser Style if and only if it adheres to the rules herein.
Like other programming style guides, the issues covered span not only aesthetic issues of formatting, but other types of conventions or coding standards as well. However, this document focuses primarily on the hard-and-fast rules that we follow universally, and avoids giving advice that isn't clearly enforceable (whether by human or tool).
This is a fork of the Google Java Style Guide, adapted and ported to the Apex Programming Language by Craig Ceremuga with the immensely helpful input and feedback of the entire NimbleUser technical consulting and engineering staff.
The guide is published as a GitHub Pages site for convenient access at nimbleuser.github.io/apex-style-guide/.
- 7/12/2017
- New standards regarding SOQL syntax have been added courtesy of @nflear.
- 6/5/2017
- New sections on testing, mocking added.
- 5/10/2017
- Table of contents added.
- Clicking on a heading will copy a direct URL for that section to your clipboard.
This guide is licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.
