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

Rest Client Reactive: Support PathParam from BeanParam #20056

Conversation

michalszynkiewicz
Copy link
Member

fixes #20027

@michalszynkiewicz michalszynkiewicz force-pushed the rest-client-reactive-support-path-param-from-bean-param branch from e0122a2 to 9cc6a05 Compare September 10, 2021 09:40
@geoand
Copy link
Contributor

geoand commented Sep 10, 2021

I believe we should backport this. WDYT?

@michalszynkiewicz
Copy link
Member Author

It feels safe. But TBH I'm under impression that passing path params in @BeanParam is a niche use case

@michalszynkiewicz
Copy link
Member Author

But if you think it's important enough, I don't mind :)

@geoand
Copy link
Contributor

geoand commented Sep 10, 2021

Let's just keep it mind

@michalszynkiewicz
Copy link
Member Author

I already added the backport label :)

@michalszynkiewicz michalszynkiewicz merged commit 8130b36 into quarkusio:main Sep 10, 2021
@quarkus-bot quarkus-bot bot added this to the 2.3 - main milestone Sep 10, 2021
@gsmet gsmet modified the milestones: 2.3.0.CR1, 2.2.4.Final Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@PathParam does not work with REST Reactive Client when mixed with BeanParam
3 participants