Is strict-uri-encode really necessary?
See original GitHub issueI am using https://github.com/Sage/jsurl to efficiently encode JSON objects in the search string, and it uses the looser URI encoding range used by browsers, including the '
character.
I also use rackt/history which uses query-string, which converts '
to %27
, which grows my urls, which makes me sad. Is there a reason the strict URI range should be used?
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
strict-uri-encode - npm
Start using strict-uri-encode in your project by running `npm i strict-uri-encode`. There are 234 other projects in the npm registry using ...
Read more >Runtine error with angular 9 : Strict mode code may not ...
Runtine error with angular 9 : Strict mode code may not include a with statement ; "strict-uri-encode": { "version" ; "resolved": "https:// ...
Read more >strict-uri-encode - npm Package Health Analysis - Snyk
An important project maintenance signal to consider for strict-uri-encode is that it hasn't seen any new versions released to npm in the past...
Read more >npm:@kaliber/use-query-string - Skypack
Update the query string, just like you would update your state. Usage no npm install needed! Copy. Open in CodePen.
Read more >Relay
n \u002F\u002F Otherwise React will be compiled in the very slow development ... DefinePlugin(env.stringified),\n \u002F\u002F This is necessary to emit hot ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@SamVerschueren the reason for #29 afaict was that markdown parsers were parsing urls with strict interpretation of the relevant RFCs which caused URLs to not be completely linkified.
IMHO the markdown parser should be fixed, because markdown is a loose format that needs to be generous regarding its inputs. After all, anybody can copy a URL from a browser and it will have the looser URI character range.
So I would be really happy if query-string could revert its ways and make the behavior in #29 optional…
❤️ thanks @SamVerschueren! Now to get rackt/history to do the same 😃