3 ms·
> Having code in a monorepo doesn't help if you don't check how your code changes affects consumers/clients of the code. It most definitely does help with that
by cryptonector 4y ago
> Having code in a monorepo doesn't help if you don't check how your code changes affects consumers/clients of the code.
It most definitely does help with that because there's fewer places to look. But if you only look at your monorepo then you'll miss a lot of things if the API you're touching is public. In this case there were consumers in the same monorepo were there not?
The issue here is that someone dropped the ball on backwards compatibility. That happens, especially when the people involved are inexperienced.
- lupire 4y agoThe original author made a huge mistake of not loudly commenting the intentionally weird behavior that was mimicking the weird POSIX API, and not having any functional tests that depended on the originally designed behavior.