You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be great if you could change the current versioning scheme to respect the most used semantic versionning:
Summary
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.
It's a pain every time we update our dependencies, we have to remember that assertj has breaking changes even though only minor version were updated.
By the way, we're stuck on version 3.17 because of this change:
Breaking change: disable bare name getter by default, to get the previous behaviour back, call Assertions.setExtractBareNamePropertyMethods(true);
What's the simplest way to get the previous behaviour? Adding this line in every test?
Regards
The text was updated successfully, but these errors were encountered:
Hi,
Would be great if you could change the current versioning scheme to respect the most used semantic versionning:
It's a pain every time we update our dependencies, we have to remember that assertj has breaking changes even though only minor version were updated.
By the way, we're stuck on version 3.17 because of this change:
What's the simplest way to get the previous behaviour? Adding this line in every test?
Regards
The text was updated successfully, but these errors were encountered: