-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Ruby 3 cores #488
Comments
The 3.x core documentation failed some tests due to reduced code coverage the last time I tried generating it. The 2.7.4 documentation should be mostly sufficient for the time being. There's a good chance that the need to download cores will be eliminated in an upcoming version, with RBS handling those duties instead. Related issue: #464 |
Fantastic. Closing this ticket. BTW, you're doing an amazing job! I just installed Solargraph again after putting it away last year for performance issues. Not sure if it's the VSCode plugin or what but I'm blown away by the progress. If I get it dialed in, I'll probably share a gist of and up-to-date VSCode configuration. There are a lot of conflicting options especially when you toss in other plugins like vs-code-rubocop, which seems to be pretty out of date. Also VSCode changes so frequently I was finding a ton of outdated configurations and advice. It would be good to have something that remains current and could be the canonical cocktail. Just to be clear, this is more to do with conflicting/outdated extensions that either I didn't configure correctly or no longer work together with Solargraph such as |
Closing. Linked issue above and it seems cores are going away. |
Hi. I just picked up a new project using ruby 3.0.2 and realized there's no cores available for ruby 3 yet.
What is the status on that? Is there anything blocking or are they just not available yet? What issues will I face by not having the core installed?
Thanks!
The text was updated successfully, but these errors were encountered: