3 ms·
"- library developers can easily see the impact their changes will have on their consumers" So, to commit breaking changes you need to file 30 Jira tickets fir
by rightbyte 8y ago
"- library developers can easily see the impact their changes will have on their consumers"
So, to commit breaking changes you need to file 30 Jira tickets first and wait for a synced commit with 30 branches? Or how do you do it? Do monorepo shops work without releases and stable versions?
If dependent projects (in use) pull your head and there is no synced development I assume you will end up with a complete legacy mess to work around other projects unit tests to get anything done.
- Shish2k 8y agoIf I update a library function to require a new parameter, then in the same commit, I will also change every application which uses that library to supply the new parameter. The promise of the monorepo is "you can pick any random commit from any point in history, and all of those applications and libraries will be compatible with each other". For major changes that are too big to migrate every user in a single commit - create a new API, do development there, migrate users from the old API to the new API, delete the old API. (I wonder if you're coming from a world where library developers and application developers don't have permission to touch each other's code? At FB at least, the library developer would be allowed to create a pull request modifying the application code - though they may need a stamp of approval from the application owner before that pull request is merged into master)
- adrianN 8y agoHow does that work in code bases where you're not authorized to change everything?
- speedkills 8y agoPainfully. File a ticket with another team and pray they don't put it off until next quarter because your teams priorities don't match up with theirs.