Justin Searls

Hey @vinistock @st0012, I'm trying to validate this actually works by setting up a project pointing at my local copy using: ```ruby gem "standard", path: "/path/to/standardrb/standard" ``` But Ruby LSP...

Thank you both for the above. I fixed the constant not defined error, but even after clearing it I'm seeing the same behavior where the plugin isn't recognized as a...

@andyw8 ahh, yes, if it's just hard-coded now that won't really scale to third-party add-ons. I was assuming the extension was phoning home to the LSP and then updating the...

**[UPDATE: Nevermind, got it running locally OK. Forgot I had to enable the format & diagnostic features on `rubyLsp.enabledFeatures`]** @andyw8 is there any way I ought to be able to...

Just released this basic version (without code actions) as v1.38.0

@vinistock @andyw8 if you would be so kind, let me know when a version of the vscode extension has shipped with the `standard` enum present and I'll go to town...

Heads up I also merged #636 which adds Code Action support (and duplicates half of Ruby LSP's rubocop integration in the process)

Thanks @andyw8. I've verified everything works, and so have updated these docs: * [Re-introduced a VS Code wiki page](https://github.com/standardrb/standard/wiki/IDE:-vscode#using-ruby-lsp) on Standard's repo documenting setup * Highlight the Ruby LSP add-on...

Hi @dorner. It's true we haven't documented all this. It'd be nice to, but I'm not sure who would find it worth their time to do. Most people start using...

Hey Nathaniel, thanks for the kind note. I appreciate your perspective and see where you're coming from. Personally, seeing `foo:,` doesn't look any more or less jarring than a naked...