refactor: pypi mapping module so that its a bit more logically named#6302
Merged
Conversation
a4166cc to
7f49231
Compare
7f49231 to
33e3dbe
Compare
2 tasks
baszalmstra
approved these changes
Jun 9, 2026
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
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.
Description
This does a large-scale refactor of the pypi mapping module, I found it was a bit hard to reason about and the types were a bit scattered. This centralizes the different mapping resolvers and does a rename of a lot of of different structs and methods. The functionality has remained identical.
Biggest changes:
DerivationOutcometo make the distinction between “not applicable”, “known no purls”, and “derived purls” explicit.How Has This Been Tested?
AI Disclosure
Tools: Codex with Pi
Checklist: