Skip to content

Switch to ruby-lsp VSCode plugin #489

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Switch to ruby-lsp VSCode plugin #489

wants to merge 1 commit into from

Conversation

ajdubovoy
Copy link
Contributor

@ajdubovoy ajdubovoy commented Jun 10, 2025

resolve https://github.com/lewagon/teachers/issues/1780

It seemed to work for me locally. The only thing I wasn't sure of is if
we needed to do anything to make it play nice with rubocop but maybe
no...?

resolve lewagon/teachers#1780

It seemed to work for me locally. The only thing I wasn't sure of is if
we needed to do anything to make it play nice with `rubocop` but maybe
no...?
@ajdubovoy ajdubovoy requested a review from Eschults June 10, 2025 08:19
Copy link
Member

@Eschults Eschults left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @ajdubovoy for testing it locally.

The only thing I wasn't sure of is if we needed to do anything to make it play nice with rubocop but maybe no...?

We should, otherwise students will be confused by linter warnings not allowing them to have a good style w/ rake and on Kitt. What are the rules enforced by default if the linter ignores the .rubocop.yml?

@ajdubovoy
Copy link
Contributor Author

I'm actually just not sure. I'm not a VSCode user and mine has never been able to run rubocop correctly and I've never figured out why 🙈

@ajdubovoy
Copy link
Contributor Author

But currently we're not installing anything separately for rubocop and I think the default behavior of ruby-lsp is to respect the config actually...I think

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

Successfully merging this pull request may close these issues.

2 participants