Repository navigation
chore: Bump StructArmed to ^0.21 and use ClassNode signatures via SignatureTypesAwareRuleInterface - #402
Merged
Conversation
…natureTypesAwareRuleInterface
samsonasik
force-pushed
the
bump-structarmed-021
branch
from
November 6, 2026 13:45
3c61509 to
231674c
Compare
Contributor
Author
|
@roxblnfk ready to review/merge 👍 |
roxblnfk
approved these changes
Nov 6, 2026
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.
What was changed
This PR Bump StructArmed to ^0.21 and make use of ClassNode signatures via new SignatureTypesAwareRuleInterface, so custom ClassSignatures tweak with use of NodeFinder no longer needed.
See commit history for details.
Why?
Simplify the logic since
signaturesalready exists in 0.21Checklist