assertj / assertj/assertj-db

versioning scheme and breaking changes

Open
#142 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
130
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Hi,

Would be great if you could change the current versioning scheme to respect the most used [semantic versionning](versioning ):

> 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.