You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this feature is not already implemented
This feature does not exist
Use case
Setting formatter: "auto" should check for add ons as well, if "ruby-lsp-rubyfmt" is available it should allow to fallback to rubyfmt instead of setting formatter to "none".
This is helpful in scenarios when we have to deal with multiple codebases with multiple code linting tools.
Description
I work with multiple codebases using different linters, rubyfmt, rubocop, etc. I can't set my formatter to "rubocop" or "auto", because I need "rubyfmt" for some.
The only workaround for me is to constantly change my formatter everytime I work on a different codebase.
It seems, "auto" only supports "rubocop" and "syntax trees" as these are Lsp Supported.
I propose to allow add-ons to be part of "auto" if it exists in the workspace.
Implementation
I did a quick tour of the codebase and I'm assuming while setting global state for the formatter we need to detect add-ons formatters too:
defdetect_formatter(direct_dependencies,all_dependencies)# NOTE: Intentionally no $ at end, since we want to match rubocop-shopify, etc.return"rubocop_internal"ifdirect_dependencies.any?(/^rubocop/)syntax_tree_is_direct_dependency=direct_dependencies.include?("syntax_tree")return"syntax_tree"ifsyntax_tree_is_direct_dependencyrubocop_is_transitive_dependency=all_dependencies.include?("rubocop")return"rubocop_internal"ifdot_rubocop_yml_present && rubocop_is_transitive_dependency"none"end
If it's accepted I can add the logic to detect add on dependencies
The text was updated successfully, but these errors were encountered:
When formatter is set to "rubocop" and rubocop doesn't exist in the Gemfile but "ruby-lsp-rubyfmt" does:
Notice the formatter is set to "rubocop_internal"
[{"response":{"data":{"__data__":"vim-lsp","init_result":{"id":1,"result":{"formatter":"rubocop_internal","capabilities":{:{},"documentFormattingProvider":true,"documentSymbolProvider":{},"experimental":{"addon_detection":true,"compose_bundle":true },"message":"lsp server already initialized"}}]
When the formatter is set to "auto" in the same codebase where ruby-lsp-rubyfmt exists:
I have checked that this feature is not already implemented
Use case
Setting formatter: "auto" should check for add ons as well, if "ruby-lsp-rubyfmt" is available it should allow to fallback to rubyfmt instead of setting formatter to "none".
This is helpful in scenarios when we have to deal with multiple codebases with multiple code linting tools.
Description
I work with multiple codebases using different linters, rubyfmt, rubocop, etc. I can't set my formatter to "rubocop" or "auto", because I need "rubyfmt" for some.
The only workaround for me is to constantly change my formatter everytime I work on a different codebase.
It seems, "auto" only supports "rubocop" and "syntax trees" as these are Lsp Supported.
I propose to allow add-ons to be part of "auto" if it exists in the workspace.
Implementation
I did a quick tour of the codebase and I'm assuming while setting global state for the formatter we need to detect add-ons formatters too:
If it's accepted I can add the logic to detect add on dependencies
The text was updated successfully, but these errors were encountered: