Clarify that this extension is not intended for general Ruby development

[shopify]

Clarify that this extension is not intended for general Ruby development

[vinistock]

This extension is not intended for Shopify use only. Both the extension's description and the README accurately state what it is: an opinionated set of extensions with automatic configuration.

Regarding the search results, I do not know how VS Code ranks extensions, but those assumptions don't seem to be accurate. The Ruby LSP also has Ruby in the name, also comes from the same verified organization, is configured to be the default extension for Ruby files in VS Code and yet is ranked below Solargraph and ruby-rubocop.

We could consider switching the name to something like Ruby extension pack, although it's unclear if that would have any effect on ranking.

[avdi]

Thanks for the reply @vinistock!

those assumptions don't seem to be accurate.

I said "naming", and the fact that a the single word "Ruby" extension is prioritized is consistent with other VSCode search results, which (I'd guess) prioritize exact matches.

We could consider switching the name to something like Ruby extension pack, although it's unclear if that would have any effect on ranking.

I can't know, but I suspect it would.

This extension is not intended for Shopify use only.

I was directed to post this here by Shopify staff engineer Kevin Newton, who repeatedly asked me to check that the issues I was seeing weren't with this extension which is "meant for Shopify developers". The experience for newcomers at present is that the topmost un-deprecated extension for Ruby is either a) for general use; or b) NOT for general use, you silly person, why are you using that one? This seems unnecessarily confusing, and a name change would probably help.

[vinistock]

who repeatedly asked me to check that the issues I was seeing weren't with this extension which is "meant for Shopify developers"

Sorry, that information was not correct. This is a generic extension pack that anyone can use, which comes with the set of extensions we usually work with at the company.

Even if you don't use all extensions in the pack, you can still use it since they won't activate automatically. For example, the Sorbet extension will do absolutely nothing unless your project is fully onboarded to Sorbet. And RDBG is a debugger client, so it also does nothing unless you explicitly start debugging with it.

The experience for newcomers at present is that the topmost un-deprecated extension for Ruby is either a) for general use; or b) NOT for general use, you silly person, why are you using that one? This seems unnecessarily confusing, and a name change would probably help.

The naming and how VS Code ranks extensions is indeed unfortunate. We'll look into how we can change the display names.

It might also be worth asking the VS Code team if they'd be open to make the default recommendation for a language always show up at the top if the user is querying for an exact language identifier.

The Rust community has a similar issue, where rust-analyzer is the default recommendation, but does not show up at the top when searching for Rust because the display name is rust-analyzer.