I'm prototyping with rsense but for now it lacks support for Windows platform. Will drop more info here later on.
rebornix
All 3 comments
@rebornix: I'm writing some code to support the Go to Definition functionality, and I'm pretty sure the structures that I'm planning on sending back will provide a substantial amount of what you want for code completion support as well. I'll create a fork for this tonight. Will be using VM:InstructionSequence in the back end to get the info for an entire workspace. Queries for the info will go to the ruby process rather than trying to create a new parser for Ruby in JavaScript.
I'm fairly sure this will give us nearly everything that is required for the rest of the Extension. (With some hard coded stuff for the StdLib/Core perhaps)
HookyQR
on 25 May 2016
any news here?
claudiug
on 27 Aug 2016
@claudiug Go to definition complete in #59. Requires better parsing of the active file to provide useful code completion.
Used my own ruby parser written in javascript to avoid excessive process spawning.
HookyQR
on 18 Sep 2016
Related issues
clxy
路
3Comments
abraham
路
4Comments
mmarinaccio
路
3Comments
chrisnicola
路
5Comments
rachsmithcodes
路
5Comments
Most helpful comment
@rebornix: I'm writing some code to support the Go to Definition functionality, and I'm pretty sure the structures that I'm planning on sending back will provide a substantial amount of what you want for code completion support as well. I'll create a fork for this tonight. Will be using VM:InstructionSequence in the back end to get the info for an entire workspace. Queries for the info will go to the ruby process rather than trying to create a new parser for Ruby in JavaScript.
I'm fairly sure this will give us nearly everything that is required for the rest of the Extension. (With some hard coded stuff for the StdLib/Core perhaps)