You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Clojure, Calva and clojure-lsp bring great API help, including rich signature help, completion, ClojureDocs, navigate to source, and such.
I find myself often switching to the Calva project and hacking there to explore the extension API. But even that is not as good as it is with Clojure code. I do a lot of googling and use bookmarks to various resources also when hacking vscode using TypeScript.
What if Joyride offered a Clojure-level experience with these things? It would become a tool for exploring the VS Code API that is better than what is offered with TypeScript. Together with #14 it would create a rapid prototyping environment for VS Code extensions that the world has never seen before. We could almost reach parity with Emacs, I think.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With Clojure, Calva and clojure-lsp bring great API help, including rich signature help, completion, ClojureDocs, navigate to source, and such.
I find myself often switching to the Calva project and hacking there to explore the extension API. But even that is not as good as it is with Clojure code. I do a lot of googling and use bookmarks to various resources also when hacking vscode using TypeScript.
What if Joyride offered a Clojure-level experience with these things? It would become a tool for exploring the VS Code API that is better than what is offered with TypeScript. Together with #14 it would create a rapid prototyping environment for VS Code extensions that the world has never seen before. We could almost reach parity with Emacs, I think.
Beta Was this translation helpful? Give feedback.
All reactions