New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please enable stub generation for Rama #2855
Comments
Just to let you know that I'm working on this, but it's trickier than I expected. Just enabling stubs is not enough, Cursive needs to know how to resolve the dataflow API which is quite unlike Clojure. |
Thank you! I imagine that could be pretty hard. IMO it does not need to be perfect, every improvement counts :-) Also, perhaps the Rama people would be willing to help with this? BTW it has been mentioned they are going to release their clj-kondo config, perhaps that could be a good guide... 🙏 |
Fix released in 1.13.1-eap9 on 2023-11-27. |
This is mostly fixed, but there are still some rough edges due to the fact that the dataflow DSL isn't really Clojure code. Some problems I'm aware of:
I plan to fix more of these but I need to get this release out, I'm interested in feedback on how well this works in practice. |
Amazing! Thank you for the super quick improvement! |
Fix released in 1.13.1 on 2023-12-07. |
Hi @holyjak ! It is awesome, many thanks! Before, Cursive was almost unusable for Rama code. Now it works really well. I have only noticed 2 tiny inconveniences:
|
Hello!
Nathan Marz's Rama is a new fascinating platform with first-class Clojure API, but similarly to Datomic it is distributed without source code, and thus barely usable in Cursive (contrary to Cider and Calva). I suppose the solution is to enable Stub generation for its namespaces, i.e. I guess com.rpl.rama, com.rpl.rama.path, com.rpl.rama.aggs, com.rpl.rama.ops, com.rpl.rama.test (see the Rama Clojure Api docs)
Thank you! 🙏
The text was updated successfully, but these errors were encountered: