deploy: 1e5fd62577
This commit is contained in:
TheDoubleH
parent
a35732a260
commit
a527835756
201 changed files with 598 additions and 1100 deletions
|
|
@ -21,25 +21,22 @@ The if..then pair, while..do pair, and for..do pair must appear on the same line
|
|||
<meta property="og:title" content="Keyword Pairs - Indentation">
|
||||
<meta property="og:description" content="Created by Microsoft, Described by waldo
|
||||
Description The if..then pair, while..do pair, and for..do pair must appear on the same line or the same level of indentation. If possible, you can align the lines it is even much more readable.
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) thenDiscussions You can find discussions on all “Best Practices” here.
|
||||
If you don’t find the discussion of this guideline, please feel free to create a new one with the same title as this article.">
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) then">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://alguidelines.dev/docs/bestpractices/keyword-pairs-indentation/"><meta property="og:image" content="https://alguidelines.dev/images/og-image-fission.png"><meta property="article:section" content="docs">
|
||||
<meta property="article:modified_time" content="2022-02-24T14:45:35+01:00"><meta property="og:site_name" content="alguidelines.dev - Business Central Design Patterns">
|
||||
<meta property="article:modified_time" content="2022-02-24T15:36:06-08:00"><meta property="og:site_name" content="alguidelines.dev - Business Central Design Patterns">
|
||||
<meta itemprop=name content="Keyword Pairs - Indentation">
|
||||
<meta itemprop=description content="Created by Microsoft, Described by waldo
|
||||
Description The if..then pair, while..do pair, and for..do pair must appear on the same line or the same level of indentation. If possible, you can align the lines it is even much more readable.
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) thenDiscussions You can find discussions on all “Best Practices” here.
|
||||
If you don’t find the discussion of this guideline, please feel free to create a new one with the same title as this article.">
|
||||
<meta itemprop=dateModified content="2022-02-24T14:45:35+01:00">
|
||||
<meta itemprop=wordCount content="82"><meta itemprop=image content="https://alguidelines.dev/images/og-image-fission.png">
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) then">
|
||||
<meta itemprop=dateModified content="2022-02-24T15:36:06-08:00">
|
||||
<meta itemprop=wordCount content="49"><meta itemprop=image content="https://alguidelines.dev/images/og-image-fission.png">
|
||||
<meta itemprop=keywords content="AL,Readability,"><meta name=twitter:card content="summary_large_image">
|
||||
<meta name=twitter:image content="https://alguidelines.dev/images/og-image-fission.png">
|
||||
<meta name=twitter:title content="Keyword Pairs - Indentation">
|
||||
<meta name=twitter:description content="Created by Microsoft, Described by waldo
|
||||
Description The if..then pair, while..do pair, and for..do pair must appear on the same line or the same level of indentation. If possible, you can align the lines it is even much more readable.
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) thenDiscussions You can find discussions on all “Best Practices” here.
|
||||
If you don’t find the discussion of this guideline, please feel free to create a new one with the same title as this article.">
|
||||
Bad code if(x=y) and(a=b) thenGood code if(x=y) and(a=b) then">
|
||||
<link rel=preload href=/scss/main.min.84a617ff0c0265eb62b5cd2929c572f4ed37dc4907d0cf068be4eb2974f6d60f.css as=style>
|
||||
<link href=/scss/main.min.84a617ff0c0265eb62b5cd2929c572f4ed37dc4907d0cf068be4eb2974f6d60f.css rel=stylesheet integrity>
|
||||
<script src=https://code.jquery.com/jquery-3.6.0.min.js integrity=sha384-vtXRMe3mGCbOeY7l30aIg8H9p3GdeSe4IFlP6G8JMa7o7lXvnz3GFKzPxzJdPfGK crossorigin=anonymous></script>
|
||||
|
|
@ -69,7 +66,7 @@ If you don’t find the discussion of this guideline, please feel free to cr
|
|||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="navbar-nav d-none d-lg-block"><input type=search class="form-control td-search-input" placeholder=" Search this site…" aria-label="Search this site…" autocomplete=off data-offline-search-index-json-src=/offline-search-index.2b0c36478a8660f3dec37e0c539508bc.json data-offline-search-base-href=/ data-offline-search-max-results=10>
|
||||
<div class="navbar-nav d-none d-lg-block"><input type=search class="form-control td-search-input" placeholder=" Search this site…" aria-label="Search this site…" autocomplete=off data-offline-search-index-json-src=/offline-search-index.446cc05ee9bff165bd123d203082adb7.json data-offline-search-base-href=/ data-offline-search-max-results=10>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
|
|
@ -80,7 +77,7 @@ If you don’t find the discussion of this guideline, please feel free to cr
|
|||
<div id=td-sidebar-menu class=td-sidebar__inner>
|
||||
<div id=content-mobile>
|
||||
<form class="td-sidebar__search d-flex align-items-center">
|
||||
<input type=search class="form-control td-search-input" placeholder=" Search this site…" aria-label="Search this site…" autocomplete=off data-offline-search-index-json-src=/offline-search-index.2b0c36478a8660f3dec37e0c539508bc.json data-offline-search-base-href=/ data-offline-search-max-results=10>
|
||||
<input type=search class="form-control td-search-input" placeholder=" Search this site…" aria-label="Search this site…" autocomplete=off data-offline-search-index-json-src=/offline-search-index.446cc05ee9bff165bd123d203082adb7.json data-offline-search-base-href=/ data-offline-search-max-results=10>
|
||||
<button class="btn btn-link td-sidebar__toggle d-md-none p-0 ml-3 fas fa-bars" type=button data-toggle=collapse data-target=#td-section-nav aria-controls=td-docs-nav aria-expanded=false aria-label="Toggle section navigation">
|
||||
</button>
|
||||
</form>
|
||||
|
|
@ -506,14 +503,6 @@ If you don’t find the discussion of this guideline, please feel free to cr
|
|||
<a href="https://github.com/microsoft/alguidelines/discussions?discussions_q=Keyword%20Pairs%20-%20Indentation" class=td-page-meta--issue target=_blank rel=noopener><i class="fab fa-github fa-fw"></i> Discussions</a>
|
||||
<a href=https://github.com/microsoft/alguidelines/issues/new class=td-page-meta--project-issue target=_blank rel=noopener><i class="fas fa-tasks fa-fw"></i> Create project issue</a>
|
||||
</div>
|
||||
<div class=td-toc><nav id=TableOfContents>
|
||||
<ul>
|
||||
<li><a href=#description>Description</a></li>
|
||||
<li><a href=#bad-code>Bad code</a></li>
|
||||
<li><a href=#good-code>Good code</a></li>
|
||||
<li><a href=#discussionshttpsgithubcommicrosoftalguidelinesdiscussionscategoriesbc-best-practicesdiscussions_qkeywordpairindentationcategory3a22bcbestpractices22><a href="https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices?discussions_q=keyword+pair+indentation+category%3A%22BC+Best+Practices%22">Discussions</a></a></li>
|
||||
</ul>
|
||||
</nav></div>
|
||||
<div class="taxonomy taxonomy-terms-cloud taxo-tags">
|
||||
<h5 class=taxonomy-title>Tag Cloud</h5>
|
||||
<ul class=taxonomy-terms>
|
||||
|
|
@ -576,11 +565,9 @@ If you don’t find the discussion of this guideline, please feel free to cr
|
|||
<div class=highlight><pre tabindex=0 style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-al data-lang=al><span style=color:#f8f8f8;text-decoration:underline> </span><span style=color:#204a87;font-weight:700>if</span><span style=color:#f8f8f8;text-decoration:underline> </span><span style=color:#ce5c00;font-weight:700>(</span>x<span style=color:#f8f8f8;text-decoration:underline> </span>=<span style=color:#f8f8f8;text-decoration:underline> </span>y<span style=color:#ce5c00;font-weight:700>) </span><span style=color:#204a87;font-weight:700>and</span><span style=color:#f8f8f8;text-decoration:underline>
|
||||
</span><span style=color:#f8f8f8;text-decoration:underline> </span><span style=color:#ce5c00;font-weight:700>(</span>a<span style=color:#f8f8f8;text-decoration:underline> </span>=<span style=color:#f8f8f8;text-decoration:underline> </span>b<span style=color:#ce5c00;font-weight:700>)
|
||||
</span><span style=color:#ce5c00;font-weight:700> </span><span style=color:#204a87;font-weight:700>then</span><span style=color:#f8f8f8;text-decoration:underline>
|
||||
</span></code></pre></div><h2 id=discussionshttpsgithubcommicrosoftalguidelinesdiscussionscategoriesbc-best-practicesdiscussions_qkeywordpairindentationcategory3a22bcbestpractices22><a href="https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices?discussions_q=keyword+pair+indentation+category%3A%22BC+Best+Practices%22">Discussions</a></h2>
|
||||
<p>You can find discussions on all “Best Practices” <a href=https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices>here</a>.</p>
|
||||
<p>If you don’t find the discussion of this guideline, please feel free to create a new one with the same title as this article.</p>
|
||||
</span></code></pre></div>
|
||||
<div class="text-muted mt-5 pt-3 border-top">
|
||||
Last modified February 24, 2022: <a href=https://github.com/microsoft/alguidelines/commit/5ee0436639455a35835c5ce88241d3fad662ee06>Added tags & categories + cleanup (5ee04366)</a>
|
||||
Last modified February 24, 2022: <a href=https://github.com/microsoft/alguidelines/commit/fb17dc9640ceef53d1f3b8bbf9e9791ef92fabbc>Removed Discussion Links. Using new Theme solution. (fb17dc96)</a>
|
||||
</div>
|
||||
</div>
|
||||
</main>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue