Fix encoding of PURL qualifiers #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lseppala
force-pushed
the
lsep/purl-qualifiers
branch
from
b4f0dcc to
b0ebf31
Compare
lseppala
force-pushed
the
lsep/purl-qualifiers
branch
from
b0ebf31 to
83edbc9
Compare
mrysav
reviewed
Jun 2, 2023
mrysav
approved these changes
Jun 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The qualifiers produced by component-detection are a dictionary of string pairs. This change fixes the encoding of qualifiers into a PURL-formatted string. Test is added to ensure constraint and assist in future changes.