Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Investigate a good way to version CARTO.js while developing next release
See original GitHub issuehttps://github.com/cartodb/cartodb and https://github.com/cartodb/deep-insights.js are pointing to v4 branch. The main issue with this is that we might merge some “breaking” changes into v4 and projects that depend on CartoDB.js (i.e: BUILDER and deep-insight.js) might break when their dependencies are updated.
We need a mechanism to ensure BUILDER and deep-insights.js point to an specific version / tag / commit.
One option that was discussed was using git tags for this.
We should use this same versioning system in deep-insights.js.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I makes sense guys, I feel @IagoLast and @rubenmoya already took a good decision about it and I’m totally with you ❤️ (except with @Jesus89 because he has just told me 👅 ).
Let’s go with tags then! 💪