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

Fixes stork path param resolution in REST Client #37757

Merged

Conversation

aureamunoz
Copy link
Member

@aureamunoz aureamunoz commented Dec 14, 2023

@aureamunoz aureamunoz force-pushed the issue-37713-fix-stork-path-resolution branch 2 times, most recently from 9b045e8 to 3d37c21 Compare December 19, 2023 13:13
@aureamunoz aureamunoz marked this pull request as ready for review December 19, 2023 13:13
@aureamunoz
Copy link
Member Author

cc @cescoffier

This comment has been minimized.

@aureamunoz aureamunoz force-pushed the issue-37713-fix-stork-path-resolution branch from 3d37c21 to 7de04b0 Compare December 19, 2023 17:19

This comment has been minimized.

@aureamunoz aureamunoz changed the title First commit for issue 37713 about stork path param resolution Fixes issue 37713 about stork path param resolution Dec 20, 2023
Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not clear why the path is still ended when received by resteasy.

@aureamunoz aureamunoz force-pushed the issue-37713-fix-stork-path-resolution branch from 7de04b0 to 4c52fbb Compare January 8, 2024 16:09

This comment has been minimized.

@aureamunoz
Copy link
Member Author

I managed to figure out where the encoding were being done. Now it should be ok!

Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch!

@cescoffier
Copy link
Member

@aureamunoz can you squash the commits?

@geoand geoand changed the title Fixes issue 37713 about stork path param resolution Fixes stork path param resolution in REST Client Jan 9, 2024
…ng when creating new URI

Related to quarkusio#37713

refactor: clean up a few commented lines

fix: use raw path and avoid double encoding, adapt tests accordingly
@aureamunoz aureamunoz force-pushed the issue-37713-fix-stork-path-resolution branch from 4c52fbb to ce206d5 Compare January 9, 2024 07:58
@geoand geoand added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jan 9, 2024
Copy link

quarkus-bot bot commented Jan 9, 2024

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@geoand geoand merged commit d0e24dc into quarkusio:main Jan 9, 2024
30 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.7 - main milestone Jan 9, 2024
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jan 9, 2024
@gsmet gsmet removed this from the 3.7 - main milestone Jan 9, 2024
@gsmet gsmet added this to the 3.6.5 milestone Jan 9, 2024
@aloubyansky aloubyansky modified the milestones: 3.6.5, 3.2.10.Final Jan 16, 2024
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 containing "/" character are not well encoded as "%2F" when using reactive rest client with Stork
5 participants