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
Following #2876, I believe we should eliminate the option to use $ after the query. I don't mind using $ as a second query component, but it should remain in the path to adhere to standard URI format. Including $ after the query ? may not be supported by most API tools and could lead to potential parsing errors or conflicts.
I think we should also establish a specific order to avoid confusion and to align more naturally with the actual composition of URI. Therefore, I propose the order as : -> $ -> ? -> #.
I don't believe these restrictions will significantly affect current behaviors too much. Instead, they may help prevent future incompatibility issues and parsing difficulties.
Following #2876, I believe we should eliminate the option to use
$
after the query. I don't mind using$
as a second query component, but it should remain in the path to adhere to standard URI format. Including$
after the query?
may not be supported by most API tools and could lead to potential parsing errors or conflicts.I think we should also establish a specific order to avoid confusion and to align more naturally with the actual composition of URI. Therefore, I propose the order as
:
->$
->?
->#
.I don't believe these restrictions will significantly affect current behaviors too much. Instead, they may help prevent future incompatibility issues and parsing difficulties.
Taking previous examples:
value
should equal42$tz=Europe/Paris
cc @jeronimoalbi @leohhhn @moul @alexiscolin wdyt ?
The text was updated successfully, but these errors were encountered: