#139 knowledge(breaking-changes): adding a parameter to an event publisher is not a signature break
The breaking-changes knowledge article now clarifies that adding a parameter to an event publisher is not a breaking change, since event subscribers bind by parameter name, not position. This aligns the article with the existing events knowledge and removes a false positive report.
- 1files
- 1AL files
- 0objects
Pull request · merged into main on 2026-09-02 by gggdttt · 1 file (+4 -2), 1 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Event subscribers bind to publishers by parameter name, not by position
- Detection now skips event publishers whose only change is an added parameter and calls such reports false positives
- Removals, retypes, renames and var flips on event publishers are still treated as breaking
- Cross-references point to the events articles, including the cases where publisher access or adding IsHandled matters
- Added the integration-event keyword
AL objects touched
microsoft/knowledge/breaking-changes/do-not-change-published-procedure-signatures.md: modified, not in the BC? snapshot
Context
- Systems: development
- From the description: “AL binds an event subscriber to its publisher by parameter name, not by position.”
Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).