mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-06 15:16:56 +01:00

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

1.7 KiB

Raw Blame History

bc-version

domain

keywords

technologies

countries

application-area

all

style

prefix

affix

spu

naming

object-name

tableextension

pageextension

as0011

all

StrongPoint objects and extension members carry the `SPU` prefix

Description

In StrongPoint repositories every new AL object name, and every new field, control or action that a table extension or page extension adds to someone else's object, starts with the mandatory affix SPU — for example codeunit 70760591 "SPU EMV Manager" or the table-extension field "SPU FB Receipt Printed". The AL-Go pipeline validates the prefix and fails the build without it; there is usually no AppSourceCop.json with mandatoryAffixes in the repository to warn earlier, so a missing prefix is only found at CI time.

Best Practice

Name every new object "SPU <App code> <Name>" and every member added to a base-app or LS Central object "SPU <App code> <Name>", following the app's existing code (for example FB for Fiscal Printing). Members of the extension's own SPU objects (fields of an SPU table, procedures of an SPU codeunit) do not need the prefix again. Report a missing prefix on a new object or extension member as major: the build will fail.

Anti Pattern

A new object or an extension field without the prefix, a suffix instead of a prefix ("Receipt Printed SPU"), or another company's affix copied from sample code. Also wrong: demanding the prefix on members of an object that is already SPU-prefixed, or on existing objects that predate the rule.

References

StrongPoint policy: AL-Go pipeline prefix validation in every SP repository (workspace CLAUDE.md, "AL Object Rules").

1.7 KiB Raw Blame History

StrongPoint objects and extension members carry the SPU prefix