From 50505a5dc5787bf5ad9f81049cc62defeda51081 Mon Sep 17 00:00:00 2001 From: waldo1001 Date: Sat, 11 Dec 2021 08:59:22 +0100 Subject: [PATCH] end else pair --- .../BCBestPractices/end-else-pair/index.md | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 content/BCBestPractices/end-else-pair/index.md diff --git a/content/BCBestPractices/end-else-pair/index.md b/content/BCBestPractices/end-else-pair/index.md new file mode 100644 index 00000000..68223d37 --- /dev/null +++ b/content/BCBestPractices/end-else-pair/index.md @@ -0,0 +1,37 @@ ++++ +title = "end else pair" +weight = 540 ++++ + +<_Created by Microsoft, Described by waldo_\> + +## Description + +The `end else` pair should always appear on the same line. + +## Bad code + +```al + if OppEntry.Find('-') then + if SalesCycleStage.Find('-') then begin + ... + end + else + ... +``` + +## Good code + +```al + if OppEntry.Find('-') then + if SalesCycleStage.Find('-') then begin + ... + end else + ... +``` + +## [Discussions](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices?discussions_q=end+else/pair+category%3A%22BC+Best+Practices%22) + +You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). + +If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file