feat: implement RFC 6570 URI templates for registry URL generation #2
Conversation
This file contains hidden or 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
Replace legacy route_patterns with standards-compliant URI templates across all 23 package types. This change prepares the codebase for IETF standardization by adopting RFC 6570 URI Template specification. - Add addressable gem dependency for URI template support - Implement URI template-based URL generation in RegistryURL class - Add uri_template, uri_template_with_version, and conditional namespace variants to purl-types.json configuration - Replace route_patterns with dynamic generation from URI templates - Maintain full backward compatibility for existing APIs - Support all existing URL patterns with standards-based templates
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.
package-url/purl-spec#538 (comment)
Replace route_patterns with standards-compliant URI templates across all 23 package types. This change prepares the codebase for IETF standardization by adopting RFC 6570 URI Template specification.
This doesn't break any ruby apis, but the json file is changed in a breaking way, I doubt anyone is using it yet though.