You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by SVilgelm August 3, 2022
Hi, as it is said in the subject. I want to use the PathParams without escaping. Is there anyway to do that?
In our case the object Ids can include the / symbols, like foo/bar/xyz:
Added `RawPathParams` options to `Client` and `Request` objects to support the path parameters with special characters, like `/`, without escaping.
Fixgo-resty#663
Discussed in #570
Originally posted by SVilgelm August 3, 2022
Hi, as it is said in the subject. I want to use the PathParams without escaping. Is there anyway to do that?
In our case the object Ids can include the
/
symbols, likefoo/bar/xyz
:the composed url will be
https://example.com/foo%2Fbar%2Fxyz
instead ofhttps://example.com/foo/bar/xyz
As a solution i would like to propose an additional
RawPathParams
option on client and request levelsThe text was updated successfully, but these errors were encountered: