Repository navigation
Preserve legacy Hamcrest class matcher semantics in AssertJ migrations - #1250
Merged
Merged
Conversation
Co-authored-by: Moderne Factory <factory@moderne.io>
Co-authored-by: Moderne Factory <factory@moderne.io>
Co-authored-by: Moderne Factory <factory@moderne.io>
23 of 76 tasks
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.
Legacy Hamcrest
is(Class)checks an object's type. The AssertJ migrations currently treat it as value equality:assertThat("value", is(String.class))becomes an assertion comparing the string withString.class. Preserve these legacy class matchers in bothHamcrestIsMatcherToAssertJandHamcrestHasPropertyToAssertJ.Distinguish the legacy overload from modern Class-valued equality using the instantiated parameter and
Matchervalue types. Retain ambiguous raw, erased, or incomplete metadata conservatively. Modern Class-valued equality and an explicitly Object-valued equality argument remain eligible for migration. The Hamcrest 1.3 dependency is test runtime only.Validation:
javac --release 8; all 21 outcomes match and all candidate outputs are idempotent. The baseline has two array compiler failures and 13 strict behavioral divergences; this candidate resolves 12.Addresses item E4 of #1211. The aggregate issue remains open.
Co-authored-by: Moderne Factory factory@moderne.io