-
Notifications
You must be signed in to change notification settings - Fork 8
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
Ripper -> Ripper-tags? #38
Comments
Hi @kwerle, thank you for your opinion!
Ripper isn't a gem. It's a stdlib. So I think it isn't ancient and it always works.
Yeah, at this time, the static analysis only works for constants and not perfect 😞
I was just curious about building analyser but now I noticed analysing Ruby code is harder than as I expected. Of course it's welcome to send PR to use ripper-tags, but please don't remove |
Yeah, following up I saw that ripper is internal. Ripper tags seems to do a really good job of ctagging - which I figure is a pretty good step in the right direction I've forked a branch of the LS and am going to take a shot at using ripper-tags with it. We'll see how it goes. It's disappointing that atom-ide does not have a lookup and outline implementation that just uses ctag data - that seems like an obvious first step for all languages. |
@kwerle did you ever get somewhere on that implementation? Did you find an alt at this point? etc / thanks! |
I use https://github.com/kwerle/ruby_language_server with vscode |
I notice this uses the ripper gem - which looks pretty ancient. Also I haven't seen it parse anything more than class names in my codebase - which seems weird. And finally, I'm a little confused by the parse code, which is probably more of a me issue.
Anyway - the ripper-tags gem seems up to date and like maybe it'd do a lot of the right things:
https://github.com/tmm1/ripper-tags
The text was updated successfully, but these errors were encountered: