News for hackers. Stuff that matters.
Re:Benefits of a Monorepo by lmm on Wednesday May 01, 2019 @07:46AM (#19796196)
Adding a new function anywhere other than the leaf project where it's used is premature. Organize around user-facing functionality. Pull out common libraries as and when you have something common enough to factor out (and, crucially, test independently), not before.
Re:Benefits of a Monorepo by jacques_chester on Wednesday May 01, 2019 @08:00AM (#19796277)
So the answer to needing to open multiple PRs is to open multiple PRs.
Re:Benefits of a Monorepo by lmm on Wednesday May 01, 2019 @09:07AM (#19796661)
The answer is to adapt your working patterns so that you never have multiple PRs on the critical path. Long-term codebase quality may require multiple PRs, but delivering user-facing functionality doesn't.
Re:Benefits of a Monorepo by amelius on Wednesday May 01, 2019 @10:18AM (#19797189)
And what if I wanted to add a method to a class? Or a method and a data member?
Re:Benefits of a Monorepo by pjmlp on Wednesday May 01, 2019 @10:49AM (#19797487)
You get the library owner team to do it and bind to the new released version.

Microservices without network headaches.