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

change nav 3-cal-coding-guidelines formatting

Browse source
This commit is contained in:
christianbraeunlich 2021-12-05 20:01:22 +01:00
parent bbfce1f9dc
commit f88c06332c
7 changed files with 5 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/NAVPatterns/3-cal-coding-guidelines/_index.md
View file

@ -17,7 +17,7 @@ Answer: all new C/AL code is bound to follow the guidelines (else it cannot be c
We're looking forward to your comments. Where you can, do provide concrete examples of the alternatives, Good and Bad. We're looking forward to your comments. Where you can, do provide concrete examples of the alternatives, Good and Bad.
[watch?v=z6skKy0pkmU&list=PLhZ3P LY7CqmVszuvtJLujFyHpsVN0Uw&index=26][anchor2] {{< youtube z6skKy0pkmU >}}

2
content/NAVPatterns/3-cal-coding-guidelines/design/index.md → content/NAVPatterns/3-cal-coding-guidelines/design/_index.md
View file

@ -6,6 +6,4 @@ weight = 490
## **Design** ## **Design**
###
Find the C/AL guidelines by expanding the menu in the left. Find the C/AL guidelines by expanding the menu in the left.

2
content/NAVPatterns/3-cal-coding-guidelines/design/by-reference-parameters/index.md
View file

@ -1,5 +1,5 @@
+++ +++
title = "By Reference Parameters.md" title = "By Reference Parameters"
weight = 280 weight = 280
+++ +++
Do not declare parameters by reference if their values are not intended to be changed. Do not declare parameters by reference if their values are not intended to be changed.

2
content/NAVPatterns/3-cal-coding-guidelines/design/with-scope-name-collision/index.md
View file

@ -4,7 +4,7 @@ weight = 1450
+++ +++
Do not use the WITH scope when it has a variable whose name is the same as a local variable. This can lead to wrong code assumptions. Do not use the WITH scope when it has a variable whose name is the same as a local variable. This can lead to wrong code assumptions.
**Given that **"Contract Type" is a field on table ServiceContractHeader, then in the following example there is a parameter name clash with the field name. Which one will be used? **Given that** "Contract Type" is a field on table ServiceContractHeader, then in the following example there is a parameter name clash with the field name. Which one will be used?
Bad code Bad code

4
content/NAVPatterns/3-cal-coding-guidelines/internally-used-dot-net-types/index.md
View file

@ -1,9 +1,7 @@
+++ +++
title = "Internally-used DotNet Types" title = "Internally used DotNet Types"
weight = 690 weight = 690
+++ +++
## **Internally used Dot Net Types**
_(Dynamics NAV 2015)_ _(Dynamics NAV 2015)_

1
content/NAVPatterns/3-cal-coding-guidelines/internationalization/_index.md
View file

@ -6,6 +6,5 @@ weight = 700
## **Internationalization** ## **Internationalization**
###
Find the C/AL guidelines by expanding the menu in the left. Find the C/AL guidelines by expanding the menu in the left.

2
content/NAVPatterns/3-cal-coding-guidelines/readability/blank-lines/index.md
View file

@ -1,5 +1,5 @@
+++ +++
title = "Blank Lines.md" title = "Blank Lines"
weight = 260 weight = 260
+++ +++
Do not use blank lines at the beginning or end of any functions, after BEGIN, before END, or inside multiline expressions. Bad code Do not use blank lines at the beginning or end of any functions, after BEGIN, before END, or inside multiline expressions. Bad code