GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
All functionality should be grouped in different gems to make it easier to extend or replace them. zero-core should only include request, response and the routing.
This stuff can then be used by other modules/gems to extend functionality further. The gem zero then becomes a basic gem, which gives users a basic package of helpers to get stuff done.
I'd suggest you structure the split in a way you get free standing libraries. So requireing zero-foo is possible without requireing zero-core. This makes sure you are doing the decoupling correctly.
To be more explicit: zero-foo should IMHO not depend on zero-core.
Moved that a bit back to first get other stuff done.