Open
Conversation
silasary
previously approved these changes
Feb 5, 2026
Contributor
Author
|
Actuallly im putting this PR on pause until the rule builder one is merged (link here once its created) |
Contributor
|
#203 is the rule builder PR |
Merged
Contributor
Author
|
with pr #203 merged ill adapt this PR to the new code, |
…into rules.py-misc-changes
Contributor
Author
I didnt mean to lie when I said that, I just got inspired when doing the preparatory merge from main to fix the conflicts |
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.
I got inspired by what I said on discord in manual-core-dev channel and I went and really looked at the rules.py file
things included in this PR so far:
@category,:half/:allthat last point can be reverted/modified if we still want it to raise an exception instead