mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 14:46:55 +01:00
36430b305c
The article's detection guidance flags 'a parameter added' on any shipped procedure. Applied to an event publisher that is bound to rather than called, this produced a false positive on BCApps PR 10278, where a trailing var parameter was appended to the existing IntegrationEvent OnAfterOpenForRecRef and the developer twice replied that adding a parameter to an existing integration event is not a breaking change. It also contradicted events/add-new-event-parameters-at-the-end, which already states that existing subscribers still bind to the leading parameters. Scope the rule to called procedures, carve out appended event parameters as additive, and keep every other event signature edit - removal, reorder, retype, var flip - in scope. Point the IsHandled case at events/do-not-add-ishandled-to-an-existing-event, which owns that semantic concern. |
||
|---|---|---|
| .. | ||
| choose-access-modifiers-deliberately.bad.al | ||
| choose-access-modifiers-deliberately.good.al | ||
| choose-access-modifiers-deliberately.md | ||
| deprecate-public-members-with-the-obsolete-lifecycle.bad.al | ||
| deprecate-public-members-with-the-obsolete-lifecycle.good.al | ||
| deprecate-public-members-with-the-obsolete-lifecycle.md | ||
| do-not-change-published-procedure-signatures.bad.al | ||
| do-not-change-published-procedure-signatures.good.al | ||
| do-not-change-published-procedure-signatures.md | ||
| do-not-expose-sensitive-data-through-public-api.bad.al | ||
| do-not-expose-sensitive-data-through-public-api.good.al | ||
| do-not-expose-sensitive-data-through-public-api.md | ||
| do-not-modify-code-already-marked-obsolete.bad.al | ||
| do-not-modify-code-already-marked-obsolete.good.al | ||
| do-not-modify-code-already-marked-obsolete.md | ||
| namespace-is-part-of-published-object-identity.bad.al | ||
| namespace-is-part-of-published-object-identity.good.al | ||
| namespace-is-part-of-published-object-identity.md | ||
| obsolete-table-fields-instead-of-deleting-them.bad.al | ||
| obsolete-table-fields-instead-of-deleting-them.good.al | ||
| obsolete-table-fields-instead-of-deleting-them.md | ||
| relocating-a-field-to-a-tableextension-is-not-a-deletion.md | ||
| unreleased-symbol-change-is-not-a-breaking-change.md | ||