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

formatted nav patterns 2 to 4

Browse source
This commit is contained in:
christianbraeunlich 2022-02-05 19:44:44 +01:00
parent 2fad891a77
commit f1f4aab1d7
55 changed files with 788 additions and 506 deletions
Download patch file Download diff file Expand all files Collapse all files

16
content/NAVPatterns/3-cal-coding-guidelines/readability/variables-declarations-order/index.md
View file

@ -2,12 +2,18 @@
title = "Variables Declarations Order"
weight = 1430
+++
Variables declarations should be ordered by type. In general, object and complex variable types are listed first followed by simple variables. The order should be the same as the object list in the object designer for C/AL objects. Afterwards come the complex variables like RecordRef, .NET, FieldRef etc. At the end come all the simple data types in no particular order. Bad code
Variables declarations should be ordered by type. In general, object and complex variable types are listed first followed by simple variables. The order should be the same as the object list in the object designer for C/AL objects. Afterwards come the complex variables like RecordRef, .NET, FieldRef etc. At the end come all the simple data types in no particular order.
StartingDateFilter@1002 : Text\[30\];
Vend@1003 : Record 23;
Bad code
```al
StartingDateFilter@1002 : Text[30];
Vend@1003 : Record 23;
```
Good code
Vend@1003 : Record 23;
StartingDateFilter@1002 : Text\[30\];
```al
Vend@1003 : Record 23;
StartingDateFilter@1002 : Text[30];
```