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

deploy: 54c74dfd7e

Browse source
This commit is contained in:
TheDoubleH 2021-12-14 21:30:13 +00:00
parent a1725fca7b
commit 359c95bfac
171 changed files with 3797 additions and 3332 deletions
Download patch file Download diff file Expand all files Collapse all files

3
bcbestpractices/readability/index.xml
View file

@ -31,6 +31,9 @@ If there is no other choice, then use the suggestions below.
word Abbreviation absence Abs account Acc accounting Acc accumulated Accum action Act activity Activ additional Add address Addr adjust Adj adjusted Adjd adjustment Adjmt agreement Agrmt allocation Alloc allowance Allow alternative Alt amount Amt amounts Amts answer Ans applies Appl application Appln arrival Arriv assembly Asm assemble to order ATO assignment Assgnt associated Assoc attachment Attmt authorities Auth automatic Auto availability Avail average Avg ba db.</description></item><item><title>Unnecessary 'else'</title><link>https://alguidelines.dev/bcbestpractices/readability/unnecessary-else/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/unnecessary-else/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description else should not be used when the last action in the then part is an exit, break, skip, quit, error.
Bad code procedure SomeProcedure() begin if IsAdjmtBinCodeChanged then Error(AdjmtBinCodeChangeNotAllowedErr,...) else Error(BinCodeChangeNotAllowedErr,...); end; Good code procedure SomeProcedure() begin if IsAdjmtBinCodeChanged then Error(AdjmtBinCodeChangeNotAllowedErr,...) Error(BinCodeChangeNotAllowedErr,...); end; Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.
If you don&amp;rsquo;t find the discussion of this guideline, please feel fee to create a new one with the same title as this article.</description></item><item><title>Unnecessary true/false</title><link>https://alguidelines.dev/bcbestpractices/readability/unnecessary-truefalse/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/unnecessary-truefalse/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description Do not use true or false keywords unnecessarily if the expression is already an logical expression.
Bad code if IsPositive() = true then Good code if IsPositive() then Bad code if Complete &amp;lt;&amp;gt; true then Good code if not Complete then Discussions You can find discussions on all &amp;ldquo;Best Practices&amp;rdquo; here.
If you don&amp;rsquo;t find the discussion of this guideline, please feel fee to create a new one with the same title as this article.</description></item><item><title>Variable Naming</title><link>https://alguidelines.dev/bcbestpractices/readability/variable-naming/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/bcbestpractices/readability/variable-naming/</guid><description>&amp;lt;Created by Microsoft, Described by waldo&amp;gt;
Description Variables that refer to a AL object must contain the objects name, abbreviated where necessary.
A variable must begin with a capital letter.