Repository navigation
Conversation
Assisted-by: ClaudeCode:claude-sonnet-5-5 Signed-off-by: lazerg <lazerg2@gmail.com>
lazerg
requested review from
Altahrim,
CarlSchwan,
leftybournes and
provokateurin
and removed request for
a team
October 31, 2026 08:05
This branch has not been deployed
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
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.
Summary
The "Check %s is invalid", "does not exist" and "is not allowed with this entity" errors in
validateOperation()printed the operation class instead of the check class, so admins were pointed at the wrong class. They now use the check class, and I added a test for the invalid case.Checklist
AI (if applicable)
Claude Code (claude-sonnet-5-5) wrote the change and test; I have not run the test suite locally.