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

Support RestResponse<T> as a return type for reactive rest client methods #19978

Merged
merged 1 commit into from
Sep 9, 2021

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Sep 7, 2021

Closes: #19966

@geoand
Copy link
Contributor Author

geoand commented Sep 8, 2021

Although it could technically be backported, it's probably best not to unless necessary

@michalszynkiewicz
Copy link
Member

How does RestResponse work with erroneous status codes? Could you add a test for this scenario?

@geoand
Copy link
Contributor Author

geoand commented Sep 8, 2021

How does RestResponse work with erroneous status codes? Could you add a test for this scenario?

It works fine if one disables the default exception mappers.
I'll add a test later on today or tomorrow morning

@geoand
Copy link
Contributor Author

geoand commented Sep 8, 2021

Test added

@geoand
Copy link
Contributor Author

geoand commented Sep 9, 2021

@michalszynkiewicz is this good for you now?

@geoand geoand merged commit 9b9d8e3 into quarkusio:main Sep 9, 2021
@quarkus-bot quarkus-bot bot added this to the 2.3 - main milestone Sep 9, 2021
@geoand geoand deleted the #19966 branch September 9, 2021 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow using RestResponse<T> as return type for rest client
2 participants