-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: encoding of special chars when encoding to string #37
fix: encoding of special chars when encoding to string #37
Conversation
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
3950688
to
49fcdf6
Compare
@steven-esser could you review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jkowalleck This looks great. Thank you for your contribution!
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
@jkowalleck v1.0.1 released to npm with your fixes: https://www.npmjs.com/package/packageurl-js/v/1.0.1 Thanks again! |
Just a heads up that this was actually a breaking change for my team. We aren't blocked per-say, just now locked into version 1.0.0. Example Failing test:
Perhaps we can add in an option to not encode ? |
https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst#rules-for-each-purl-component
|
* fix: encoding of special chars when encoding to string * docs: changelog for package-url#37 Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
toString()
is called