-
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
hotfix: properly handle purl encoding #61
Conversation
* remove unneed exception raising for the version param * do not skip URL encoding `:` and `+` characters * add test cases from old issues refs: #45, #46, #57 Signed-off-by: Steven Esser <[email protected]>
test/data/test-suite-data.json
Outdated
@@ -122,7 +122,7 @@ | |||
{ | |||
"description": "docker uses qualifiers and hash image id as versions", | |||
"purl": "pkg:docker/customer/dockerimage@sha256:244fd47e07d1004f0aed9c?repository_url=gcr.io", | |||
"canonical_purl": "pkg:docker/customer/dockerimage@sha256:244fd47e07d1004f0aed9c?repository_url=gcr.io", | |||
"canonical_purl": "pkg:docker/customer/dockerimage@sha256%3A244fd47e07d1004f0aed9c?repository_url=gcr.io", |
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.
The official test input says this should be unencoded (':').
I recommend keeping test-suite-data.json exactly the same as in the spec repository and making a separate file for tests that are unique to this repository. That makes it easier to ensure this implementation matches the spec, easier to update the copy of the test suite file, and easier to find tests that could be added to the spec.
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.
Good point.
Any updates when this will be merged? |
7ba01c1
to
2a4018a
Compare
Signed-off-by: Steven Esser <[email protected]>
2a4018a
to
f3ee1ba
Compare
Is there an ETA on getting this in? |
Closing as covered by #71 |
v2.0.0 has been published 🎉 |
:
and+
charactersrefs: #45, #46, #57