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
Currently, gentleman supports a non-standard :<name> notation for defining replacement path tokens in a URI, excluding the query parameters.
Level 1 of the proposed standard: rfc6570 specifies the use of {<name>} notation for replacement tokens in both the path and the query parameters.
In order to support the use of URIs obtained from HATEOAS links which may follow the rfc6570 standard, gentleman should support the standard notation. Additionally, it should support replacement of tokens in the query parameters in addition to the path.
The text was updated successfully, but these errors were encountered:
Currently, gentleman supports a non-standard
:<name>notation for defining replacement path tokens in a URI, excluding the query parameters.Level 1 of the proposed standard: rfc6570 specifies the use of
{<name>}notation for replacement tokens in both the path and the query parameters.In order to support the use of URIs obtained from HATEOAS links which may follow the rfc6570 standard, gentleman should support the standard notation. Additionally, it should support replacement of tokens in the query parameters in addition to the path.
The text was updated successfully, but these errors were encountered: