Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Revert "Add unit tests and knowledge files for BC domain context"

Browse source 
This reverts commit 7fbb121c24.
This commit is contained in:
Jesper Schulz-Wedde 2026-04-22 14:03:09 +02:00
parent 7fbb121c24
commit 9dad34f48a
18 changed files with 1 additions and 1170 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -52,7 +52,7 @@ Every knowledge file is a markdown file with mandatory YAML frontmatter. Files t
```yaml
---
bc-version: [26..28] # BC versions this applies to; use [1..99] for universal content
bc-version: [26..28] # BC versions this applies to
domain: performance # security | performance | ux | telemetry | ...
keywords: [query, filtering, partial] # free-text tags for retrieval
technologies: [al] # al | javascript | powershell | ...
@ -63,8 +63,6 @@ application-area: [all] # finance | manufacturing | jobs | [all]
All six fields are required. The schema is locked — changes require a PR approved by both maintainers.
**`bc-version` convention.** Content that describes version-specific behaviour (a query optimizer change in BC 26, a security API renamed in BC 27) lists the specific major versions or a tight range. Content that describes canonical BC concepts which are stable across every supported release — domain knowledge like `Codeunit 12 (Gen. Jnl.-Post Line)`, `T15 G/L Account`, VAT posting setup, the dimensions model — uses `bc-version: [1..99]`. This signals "applies to every BC version past, present, and future" without forcing an annual bump of every file when a new release ships.
### Sections
Every knowledge file must contain a `## Description` section. The following sections are optional but recommended: