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.
Is this project still maintained?
See original GitHub issueIt seems like this project is no longer being actively maintained – the last minor release was close to three years ago and it doesn’t support the Clojure CLI (which was released over four years ago). However, it still shows up in the VS Code marketplace and it somewhat misleadingly uses the official Clojure logo which makes it look authoritative.
Did you get permission to use the logo? See https://groups.google.com/g/clojure/c/mc-JzjXspe0/m/ol17UfGrqbQJ for some discussion about that.
Given the massive uptake of Calva for VS Code and the huge difference in functionality between Calva and this project, I wonder if you would mind a) changing the logo for the extension to make it look less like an official “core” project and b) adding a note to your README that indicates Calva is the actively-maintained, recommended extension for Clojure these days (so it will show up in the VS Code Extensions list when folks search for Clojure)?
I think this would be much less confusing for Clojurians starting to use VS Code.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 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
@avli yes to both questions. Current will not be forced off the extension but will see that it is deprecated.
Looks good in the Extensions view in VS Code – thank you!