Skip to content
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

Reorganize purldb repo #439

Open
Tracked by #515
JonoYang opened this issue May 28, 2024 · 2 comments
Open
Tracked by #515

Reorganize purldb repo #439

JonoYang opened this issue May 28, 2024 · 2 comments

Comments

@JonoYang
Copy link
Member

JonoYang commented May 28, 2024

We have a lot of related code in different places. For example, the minecode/visitor and minecode/mapper modules have code that is logically together, but is currently separated. Reorganizing the repo helps with clarity and focuses the specific workflow we want.

We should organize code to reflect the multi-level data collection we want to do:

  1. Collect name, version, checksum
  2. Collect metadata from registry
  3. Collect package and scan

See also:

@JonoYang
Copy link
Member Author

JonoYang commented Aug 8, 2024

A start would be to merge the visitor and mapper files of each repo type and then place that in a new module called miners

@JonoYang
Copy link
Member Author

The minecode visitors and mapper modules have been combined into the miners module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant