We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Customization.matches(Object actual, Object expected) method inverts the order of the parameters compared to the main compare methods, e.g. JSONCompare.compareJSON(String expectedStr, String actualStr, JSONComparator comparator) and JSONAssert.assertEquals(String expectedStr, JSONObject actual, boolean strict).
Customization.matches(Object actual, Object expected)
JSONCompare.compareJSON(String expectedStr, String actualStr, JSONComparator comparator)
JSONAssert.assertEquals(String expectedStr, JSONObject actual, boolean strict)
Please change the code to use a consistent ordering to prevent confusion when writing custom comparison Customizations.
Customization
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
Customization.matches(Object actual, Object expected)
method inverts the order of the parameters compared to the main compare methods, e.g.JSONCompare.compareJSON(String expectedStr, String actualStr, JSONComparator comparator)
andJSONAssert.assertEquals(String expectedStr, JSONObject actual, boolean strict)
.Please change the code to use a consistent ordering to prevent confusion when writing custom comparison
Customization
s.The text was updated successfully, but these errors were encountered: