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

16
content/docs/vibe-coding/al-naming-conventions.md
View file

@ -65,24 +65,24 @@ SalesPostingTests.Codeunit.al
## Rule 3: Variable and Function Naming
### Intent
Use consistent naming conventions for variables and functions to improve code readability. Use camelCase for variable and function names, descriptive names that clearly indicate purpose, and avoid abbreviations unless they are well-known business terms. Use consistent parameter naming in procedures.
Use consistent naming conventions for variables and functions to improve code readability. Use PascalCase for variable and function names, descriptive names that clearly indicate purpose, and avoid abbreviations unless they are well-known business terms. Use consistent parameter naming in procedures.
### Examples
```al
// Good examples - Variables
var
customerLedgerEntry: Record "Cust. Ledger Entry";
totalAmount: Decimal;
discountPercentage: Decimal;
isValidTransaction: Boolean;
CustomerLedgerEntry: Record "Cust. Ledger Entry";
TotalAmount: Decimal;
DiscountPercentage: Decimal;
IsValidTransaction: Boolean;
```
```al
// Good examples - Functions
procedure calculateCustomerBalance(customerNo: Code[20]): Decimal
procedure validateSalesDocument(var salesHeader: Record "Sales Header")
procedure updateInventoryQuantity(itemNo: Code[20]; quantity: Decimal)
procedure CalculateCustomerBalance(CustomerNo: Code[20]): Decimal
procedure ValidateSalesDocument(var SalesHeader: Record "Sales Header")
procedure UpdateInventoryQuantity(ItemNo: Code[20]; Quantity: Decimal)
```
## Rule 4: Parameter Naming in Event Subscribers