Fix Is(Not)Abstract expression so that it does not ignore final classes#560
Closed
X-Coder264 wants to merge 1 commit intophparkitect:mainfrom
Closed
Fix Is(Not)Abstract expression so that it does not ignore final classes#560X-Coder264 wants to merge 1 commit intophparkitect:mainfrom
X-Coder264 wants to merge 1 commit intophparkitect:mainfrom
Conversation
Collaborator
|
Thanks for the pr! |
fain182
pushed a commit
that referenced
this pull request
Jan 25, 2026
This test replicates the issue described in PR #560 where IsNotAbstract incorrectly filters out final classes when used in a that() clause. The test creates a scenario with: - Final classes with correct/incorrect naming - Abstract classes (should be filtered out) - Normal classes with incorrect naming Expected behavior: IsNotAbstract should include final classes in the filter since final classes are, by definition, non-abstract. Current behavior: Test fails with 1 violation instead of expected 2, demonstrating that final classes are incorrectly excluded.
fain182
pushed a commit
that referenced
this pull request
Jan 25, 2026
This fixes the issue described in PR #560 where IsNotAbstract incorrectly excluded final classes when used in that() clauses. Root cause: appliesTo() was implementing two different semantics: 1. Type filtering: "Does this property apply to this type?" 2. Condition checking: "Does this class match the condition?" This caused final classes to be excluded from IsNotAbstract filters, even though final classes ARE non-abstract by definition. Changes: - IsAbstract/IsNotAbstract: Remove isFinal() check from appliesTo() Final classes can be checked for abstractness (they're always non-abstract) - IsFinal/IsNotFinal: Remove isAbstract() check from appliesTo() Abstract classes can be checked for finality (they're always non-final) New semantics for appliesTo(): - Returns true if the property can be semantically verified for this type - Only excludes interface/trait/enum where abstract/final concepts don't apply - Does NOT exclude mutually exclusive states (abstract/final) All 350 tests pass, including new integration tests that verify: - IsNotAbstract in that() now includes final classes - IsNotAbstract in should() correctly validates all class types
Collaborator
|
The pr #561 should fix this problem globally, @X-Coder264 can you test if it solves your problem? Thanks! |
Author
Collaborator
|
Released |
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.
We have this rule in our codebase (and other similar rules too):
Basically we want to make sure that all test class names in our testsuite that extend the base
EndToEndTestCaseclass that are not abstract classes themselves must end withEndToEndTest.After #454 this no longer works as the logic early returns in
\Arkitect\Rules\Specs::allSpecsAreMatchedBybecause\Arkitect\Expression\ForClasses\IsNotAbstract::appliesToreturnsfalsefor final classes (and all our test classes are final) and because of that the\Arkitect\Expression\ForClasses\HaveNameMatchingexpression never gets evaluated so no violations are reported.After this fix
appliesTowould returntrueand everything would continue to work as it did prior to that #454 PR.