5 ms·
Totally agree. If the new version of a library requires a slightly updated usage; please just give me simple examples of how to update my code. Include a simple
by brody_hamer 6y ago
Totally agree. If the new version of a library requires a slightly updated usage; please just give me simple examples of how to update my code. Include a simple regex. And while we’re are it, let’s standardize how we provide those upgrade scripts. So when snyk tells me there’s and issue, it also easy to find and apply the necessary code changes (at least for the simplest 90% of cases).
Like python’s “2to3”.
It’s not a magic bullet; the developer still benefits from thorough testing, but I think changelogs could stand to improve in a lot of projects.
- andy_ppp 6y agoI think codemod is probably one such tool: https://github.com/facebook/codemod https://github.com/facebook/codemod
- nlitened 6y agoHow about something new: release only backward-compatible updates unless absolutely necessary.
- peteradio 6y agoFor real. If its not acting the same, then its not the same thing, give it a different name and release your 0.1. I guess maybe we run out of namespace with this methodology? Suddenly we end up with software named axsladkjfaksldjf, and then hackers start camping on axsladejfaksldjf
- nlitened 6y agoThe name space is not a problem, in my opinion. If you have a library sdaffj, and you want to release a new, incompatible version, release it under the name sdaffj2, next incompatible version under name sdaffj3, etc.
- raverbashing 6y agoOr you know, library deprecates "easy way of doing something" replacing it with "weird and convoluted" way of doing this again without any guidance of how to do the old thing And unless the old way was genuinely bad/hard, why deprecate?