Skip to content
New issue

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

OpenFeign 10.7.4, 10.7.3 and 10.8 break backward compatibility #1194

Closed
sofax opened this issue Mar 20, 2020 · 6 comments
Closed

OpenFeign 10.7.4, 10.7.3 and 10.8 break backward compatibility #1194

sofax opened this issue Mar 20, 2020 · 6 comments
Labels
chore For issues related to technical debt and other non-functional tasks feedback provided Feedback has been provided to the author good first issue Issues that are good for first time contributors to tackle

Comments

@sofax
Copy link

sofax commented Mar 20, 2020

Updating from v10.7.2 to v10.7.3, v10.7.4 or v10.8 breaks existing code, because Request.requestBody() was removed. The following line won't compile anymore:

      final Request.Body body = request.requestBody();
@kdavisk6
Copy link
Member

@sofax, that move was intentional. requestBody() was an internal method that mistakenly was made public. Use Request#body.

@kdavisk6 kdavisk6 added the feedback provided Feedback has been provided to the author label Mar 29, 2020
@sofax
Copy link
Author

sofax commented Apr 16, 2020

That means we will NEVER be able to update OpenFeign, because we deliver artifacts that MUST NOT break existing code with minor, or - as in this case - even patch level version upgrades.

Sorry, guys, this is very bad! :(

@velo
Copy link
Member

velo commented Apr 16, 2020

hi @sofax feel free to submit a PR with a fix for this.

Keep in mind the method will be removed for feign 11.

@sofax
Copy link
Author

sofax commented Apr 17, 2020

We are more interested in bug fixes for the 10.x branch, not a major upgrade. Breaking the code with a patch release violates the idea of semantic versioning, which I thought/was hoping you are adhering to. If the exposition of an internal API in a previous release was an accident you should provide a workaround for it instead of just hiding it again, or you will make all upcoming bugfix releases unusable for most people.

We will (have to) stick with v10.7.2 then.

@velo
Copy link
Member

velo commented Apr 17, 2020

We will (have to) stick with v10.7.2 then.

Or, you can get the souces and submit a PR restoring the missing method
If you really care about this, recommend doing it sooner rather than later.

Also, feel free to also include the necessary tooling to prevent API for ever being broken again.

@kdavisk6
Copy link
Member

kdavisk6 commented Apr 19, 2020

#1200 addresses additional fixes

@kdavisk6 kdavisk6 reopened this Apr 19, 2020
@velo velo added chore For issues related to technical debt and other non-functional tasks good first issue Issues that are good for first time contributors to tackle labels May 4, 2020
@velo velo closed this as completed May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore For issues related to technical debt and other non-functional tasks feedback provided Feedback has been provided to the author good first issue Issues that are good for first time contributors to tackle
Projects
None yet
Development

No branches or pull requests

3 participants