bcquality/custom
Paulius Urbanas 5149da25ba Add StrongPoint custom knowledge layer
Eight organization rules in custom/knowledge, each overriding or
supplementing the Microsoft layer for StrongPoint repositories:

- style/spu-prefix-on-objects-and-extension-members
- style/cyclomatic-complexity-is-not-a-gate-in-sp-repos (LC0010 = Info)
- ui/keep-tooltips-on-sp-page-fields (AA0218 = Error, LC0064 off;
  overrides microsoft ui/bound-page-field-inherits-source-field-tooltip)
- data-modeling/sp-field-names-fit-30-chars-with-prefix (AL0468 = Error)
- events/change-ls-central-behaviour-through-its-events
- web-services/device-io-goes-through-sp-device-manager
- appsource/sp-id-ranges-are-not-checked-by-as0084 (AS0084 = None)
- upgrade/sp-released-ids-never-change

Sources: sp.ruleset.json across SP repositories, SPUFBUpgrade pattern in
SP-LSC-Fiscal-Printing, observed LS Central and Device Manager usage.
Verified: all eight are indexed by Build-KnowledgeIndex.ps1, and a review
of a probe app applied the ToolTip rule as major and suppressed the
Microsoft article by layer precedence.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-25 13:50:52 +03:00
..
knowledge Add StrongPoint custom knowledge layer 2026-09-25 13:50:52 +03:00
skills Add initial project structure with .gitignore, LICENSE, README, and CODEOWNERS 2026-04-17 05:56:10 +02:00
README.md Improve partner onboarding and documentation navigation (#174) 2026-09-09 17:31:03 +02:00

Custom layer

This folder is the template for partner- and customer-specific overrides. Use it to add knowledge and skills that apply to your organization but are not appropriate for the shared Microsoft or Community layers.

Structure

custom/
├── knowledge/    # Your organization's knowledge files (same format as /microsoft/knowledge/)
└── skills/       # Your organization's action skills

How to use

Use a fork or organization-controlled copy of BCQuality, not the upstream repository or your AL app's source folder. Confirm git remote get-url origin points at your repository before adding custom content. Upstream does not accept custom rules.

Follow Customizing BCQuality for a worked rule, plugin configuration, installing your fork, and keeping it up to date. Adding a rule here does not update an existing upstream plugin installation; your host must consume your copy.

Knowledge files follow READ and action skills follow DO. With the Custom layer enabled, applicable custom knowledge overrides contradictory Community or Microsoft guidance. The report records the displaced article; non-conflicting guidance remains additive.