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

2
content/docs/vibe-coding/al-guidelines-rules.md
View file

@ -36,7 +36,7 @@ The following rule sets provide comprehensive guidance for AL development:
## Key Guidelines Summary
- **File Naming**: Use `<ObjectName>.<ObjectType>.al` pattern consistently
- **Code Style**: Use 2-space indentation and camelCase for variables, PascalCase for objects
- **Code Style**: Use two space indentation and PascalCase for variables, PascalCase for objects
- **Folder Structure**: Organize by feature (`src/feature/subfeature/`) not by object type
- **Performance**: Filter data early, use temporary tables, avoid unnecessary loops
- **Events**: Prefer integration events over direct modifications for extensibility