Skip to content
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.

ruby-lint is a mess with Rails. It still in use by the community? #225

Closed
ghost opened this issue Nov 28, 2017 · 5 comments
Closed

ruby-lint is a mess with Rails. It still in use by the community? #225

ghost opened this issue Nov 28, 2017 · 5 comments

Comments

@ghost
Copy link

ghost commented Nov 28, 2017

Your environment

  • vscode-ruby version: 0.15.0
  • Ruby version: ruby 2.4.2p198 (2017-09-14 revision 59899) [x64-mingw32]
  • VS Code version: 1.18.1 and 1.19.0-insider
  • Operating System: Windows 10 latest

Expected behavior

ruby-lint OK with Rails.

Actual behavior

ruby-lint is a mess with Rails.

image

I see ruby-lint is old and unmanteined. Is it still in use by the community? We really need it?

@goronfreeman
Copy link

I've never heard of anyone using ruby-lint. The de facto Ruby linter is rubocop.

@ghost
Copy link
Author

ghost commented Dec 12, 2017

In this package Readme:

image

@wingrunr21
Copy link
Collaborator

Closing for issue cleanup. Apologies if this is still an issue. We are working to improve the core extension experience.

@richjdsmith
Copy link

Any chance we could open this and use this thread as a discussion about dropping ruby-lint from the recommended available Linter Hooks?

@wingrunr21
Copy link
Collaborator

Nope because I'm already planning on dropping support: #317 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants