3 ms·
> Since you're only doing this when you've got breaking changes coming in anyway, i.e., you've already got to fix the code Just because the module broke compat
by toast0 6y ago
> Since you're only doing this when you've got breaking changes coming in anyway, i.e., you've already got to fix the code
Just because the module broke compat doesn't mean you were using the things that broke though. Maybe they dropped or changed functions that you didn't use.
- xh-dude 6y agoThen you don’t have breaking changes, though?
- srtjstjsj 6y agoBreaking and Naming is a property of the whole package, not the subset one client uses.
- dilap 6y agoIt's interesting that your comment and xyzzy_plugh's comment make opposite points! But you're right, in some cases the breaking changes won't break you. In any case, I do think it's worth having a dead-easy way to fix the imports, rather than having to fuss about with grep. (And what if you could actually ship rules to transform code to the upgraded version? That would be cool...)