mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-07 15:46:55 +01:00
Fix remaining READ-convention sample links across this PR's 18 articles
The same plain-backtick "See sample: \`x.good.al\`." form fixed on al-methods-limited-during-write-transactions (PR #161) turned up repo-wide on 15 more of this PR's articles - Knowledge-Retrieval.ps1 requires the markdown-link form to associate a sample with its article. All 16 fixed; the four local validators (frontmatter, knowledge-index, knowledge-retrieval, review-fixtures, skill-index) pass.
This commit is contained in:
parent
faa0bceb86
commit
b983a6da57
16 changed files with 32 additions and 32 deletions
|
|
@ -19,10 +19,10 @@ All AL identifiers — variables, procedures, parameters, fields, object names,
|
|||
|
||||
Write every identifier in English, and translate developer intent rather than transliterating it — when a requirement is described in another language, the resulting variable, procedure, and field names should still read as English. Captions and tooltips may carry target-language text in the source file, with locale translations managed through XLIFF.
|
||||
|
||||
See sample: `al-identifiers-english.good.al`.
|
||||
See sample: [`al-identifiers-english.good.al`](al-identifiers-english.good.al).
|
||||
|
||||
## Anti Pattern
|
||||
|
||||
Using native-language identifiers such as a Danish variable or procedure name in AL source code, relying on the fact that the code still compiles and runs correctly. This makes the code unreadable to non-native-language contributors and mixes localization concerns into source that should stay language-neutral.
|
||||
|
||||
See sample: `al-identifiers-english.bad.al`.
|
||||
See sample: [`al-identifiers-english.bad.al`](al-identifiers-english.bad.al).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue