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

Consider splitting into more projects #15

Open
dlmr opened this issue Dec 17, 2015 · 2 comments
Open

Consider splitting into more projects #15

dlmr opened this issue Dec 17, 2015 · 2 comments
Labels

Comments

@dlmr
Copy link
Member

dlmr commented Dec 17, 2015

Given the work that is currently done in #12 it might be a smart idea to split the functionality into at least three projects, potentially four.

  • roc-config - Only configuration management
  • roc-cli - The CLI parts
  • roc-validation - The validation parts
  • (roc-documentation - The "documentation" generation parts)

This should be further investigated and decided before publishing version 1.0.

@dlmr dlmr added this to the v1.0 milestone Dec 17, 2015
@dlmr dlmr added the question label Dec 18, 2015
@dlmr dlmr assigned androa and andreasrs and unassigned androa and andreasrs Jan 4, 2016
@dlmr dlmr removed this from the v1.0 milestone Jan 4, 2016
@dlmr dlmr unassigned androa Mar 17, 2016
@alexewerlof
Copy link
Contributor

Can Lerna from Babel origin be of help?

@dlmr
Copy link
Member Author

dlmr commented Aug 15, 2016

It can definitely be, but I'm uncertain if we truly need it and if it is the best solution. When we are ready to do a split, after the initial release I think, we should investigate what option will suit us the best.

Some reading resources for the future:
https://github.com/boennemann/alle
http://staltz.com/setting-up-a-javascript-monorepo.html

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

No branches or pull requests

4 participants