Enables assertions chaining #3304
Closed
Conversation
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
Contributor
|
Changing return types is a binary-incompatible change. |
Author
|
Do you care about binary compatibility of a return type in a test util class? |
Member
|
Since both |
Author
|
Do you see a risk here? |
Member
|
Yes. I'm sorry, but such change can't be accepted for 1.x, however, you are free to propose this against 2.x. |
Author
|
No problem. |
Member
|
It's not about releasing it to prod. If we break our public API, we break their code bases. Just because it's their test code does not mean we have a lower commitment to not breaking it.
Please get involved in the 2.x effort which is just getting underway for API related changes.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fluent assertions make the code much more readable.
This change is backward compatible.