kevva / kevva/strict-uri-encode
State differences from encodeURIComponent
Open
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
The readme says:
> A stricter URI encode adhering to [RFC 3986](http://tools.ietf.org/html/rfc3986)
I assume this means stricter than `encodeURIComponent`? If so, it would be good to state that in the readme, and list which extra characters this library encodes compared to `encodeURIComponent`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the README section describing RFC 3986 compliance and compare the library's behavior with JavaScript's encodeURIComponent. Document whether the library is stricter and identify the additional characters it encodes, then verify the README accurately reflects the comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100