mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 09:26:52 +01:00
9a4198eb28
Most of the corpus — FindSet/SetLoadFields/CalcFields patterns, permission sets, SingleInstance codeunits, DataClassification, IsolatedStorage, transaction scope, SecretText — describes BC platform behaviour that is identical across supported versions. The seed [26..28] range on every file implied a version-specificity the content does not actually have, and there was no way to express "applies to every version" in the schema the way [w1] and [all] already do for countries and application-area. Extend the v1 schema with a universal sentinel for bc-version, parallel to the sentinels already defined for the other dimensions: bc-version: [all] # applies to every BC version [all] is mutually exclusive with explicit versions. Range shorthand ([26..28]) and explicit lists ([26, 27, 28]) continue to work for files genuinely tied to a version-gated API or deprecation. Update read.md (field definition, matching semantics, partial-context rule), write.md (default to [all], use ranges only with a concrete reason), README.md (frontmatter example), and the CI validator. All forty existing knowledge files and the three action skills convert to [all]; none of the current content is version-gated. Validator passes. |
||
|---|---|---|
| .. | ||
| compose-secrets-with-secretstrsubstno.bad.al | ||
| compose-secrets-with-secretstrsubstno.good.al | ||
| compose-secrets-with-secretstrsubstno.md | ||
| do-not-expose-sensitive-data-in-event-publishers.bad.al | ||
| do-not-expose-sensitive-data-in-event-publishers.good.al | ||
| do-not-expose-sensitive-data-in-event-publishers.md | ||
| follow-least-privilege-in-permission-sets.bad.al | ||
| follow-least-privilege-in-permission-sets.good.al | ||
| follow-least-privilege-in-permission-sets.md | ||
| never-hardcode-secrets-in-al.bad.al | ||
| never-hardcode-secrets-in-al.good.al | ||
| never-hardcode-secrets-in-al.md | ||
| prefer-azure-key-vault-for-production-secrets.md | ||
| use-indirect-permissions-for-elevated-access.bad.al | ||
| use-indirect-permissions-for-elevated-access.good.al | ||
| use-indirect-permissions-for-elevated-access.md | ||
| use-inherent-permissions-to-grant-minimal-access.bad.al | ||
| use-inherent-permissions-to-grant-minimal-access.good.al | ||
| use-inherent-permissions-to-grant-minimal-access.md | ||
| use-isolated-storage-for-module-and-company-secrets.bad.al | ||
| use-isolated-storage-for-module-and-company-secrets.good.al | ||
| use-isolated-storage-for-module-and-company-secrets.md | ||
| use-nondebuggable-when-parsing-secrets.bad.al | ||
| use-nondebuggable-when-parsing-secrets.good.al | ||
| use-nondebuggable-when-parsing-secrets.md | ||
| use-secrettext-for-credentials.bad.al | ||
| use-secrettext-for-credentials.good.al | ||
| use-secrettext-for-credentials.md | ||
| use-secrettext-with-httpclient.bad.al | ||
| use-secrettext-with-httpclient.good.al | ||
| use-secrettext-with-httpclient.md | ||