Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update AL coding guidelines to use PascalCase for variable and function names

Browse source 
- Corrected naming conventions in the AL code style documentation to specify PascalCase instead of camelCase for variables and functions.
- Adjusted examples throughout the documentation to reflect the updated naming conventions.
- Enhanced clarity in performance guidelines by renaming procedures for better understanding.
This commit is contained in:
Dmitry Katson 2025-07-30 22:08:25 +08:00
parent 6b3f522a16
commit 2a805b20dc
6 changed files with 15 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/docs/vibe-coding/al-code-style.md
View file

@ -11,7 +11,7 @@ alwaysApply: true
These rules ensure consistent code structure and organization across AL projects, making code more maintainable and AI-assistant friendly.
## Style guidelines for AL code
- Always use camelCase for variable and function names.
- Always use PascalCase for variable and function names.
- Use PascalCase for object names (e.g., tables, pages, reports).
- Maintain a consistent indentation style (2 spaces preferred).
@ -22,7 +22,7 @@ These rules ensure consistent code structure and organization across AL projects
## Rule 1: Consistent Indentation and Formatting
### Intent
Maintain consistent code formatting to improve readability and enable better AI understanding of code structure. Use 2-space indentation consistently throughout your project and maintain consistent formatting within functions and procedures.
Maintain consistent code formatting to improve readability and enable better AI understanding of code structure. Use indentation with two spaces consistently throughout your project and maintain consistent formatting within functions and procedures.
### Examples