Gno: An interpreted, stack-based Go virtual machine to build succinct and composable apps + gno.land: a blockchain for timeless code and fair open-source.
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:
valueshould equal42$tz=Europe/Pariscc @jeronimoalbi @leohhhn @moul @alexiscolin wdyt ?