Repository navigation
docs(AC0002): document setup-table exemption - #199
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the AC0002 setup-table exemption from ALCops/Analyzers#575.
### Exceptionsection on the AC0002 page. Setup tables are not reported because their single record always has a blank key and no other table relates to it, so a rename or delete has nothing to cascade to.Primary Key/PrimaryKey, or a parameterlessGetRecordOnceprocedure), not by checking inbound relations. It includes an example.Primary Key, or a key namedPK/CodewithoutGetRecordOnce) and says how to opt out with an explicitNotBlank = false.Hugo build with
--panicOnWarningpasses.Companion to ALCops/Analyzers#579.
🤖 Generated with Claude Code