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

Have a way to declare, visualize, and prevent module dependencies #258

Open
BigLep opened this issue Apr 5, 2023 · 0 comments
Open

Have a way to declare, visualize, and prevent module dependencies #258

BigLep opened this issue Apr 5, 2023 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@BigLep
Copy link
Contributor

BigLep commented Apr 5, 2023

Done Criteria

Maintainers are equipped with the tooling to prevent all the modules from depending on each other. (Please correct) @BigLep assumes the way to do this is to have:

  1. a way to declare module dependencies
  2. visualize them
  3. enforce that certain modules aren't depended on

Why Important

This is critical for hitting Boxo's modularity goals. Just because they live together and version together doesn’t mean all depend on each other

Notes

There was discussion about this in ipfs/kubo#8543 but I'm sure how relevant it is anymore.

@BigLep BigLep added the need/triage Needs initial labeling and prioritization label Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant