-
Notifications
You must be signed in to change notification settings - Fork 47
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
Confusion on official cli binary name #232
Comments
Note: I am a fan of |
@chalkygames123, would you be able to provide some guidance? |
Nah, I'm not a maintainer of this project. But I'm a fan of |
@mstruebing, are you a maintainer? Would you be able to weigh in on this? |
So, my intention to add Do you have a strong opinion if it should rather be ec or editorconfig-checker? I currently think it should be |
I would side with |
Having an alias binary is okay, but having only that one is not a good idea, IMO. |
@mstruebing, can we close this issue with the acceptance of |
If truly the confusion is to be removed, then I think it would be important to standardize it across the board. Currently the If |
Hello,
When this tool is installed, should the binary/cli tool be called
editorconfig-checker
orec
. Typically, shorthand names likeec
are reserved for system tools such asls
,cat
, etc.When running
go install github.com/editorconfig-checker/editorconfig-checker/cmd/editorconfig-checker@latest
, the binary name iseditorconfig-checker
. However, on the releases page, the binary isec
. This has sparked some discussions across a few plugins using this plugin:jose-elias-alvarez/null-ls.nvim#1282
jay-babu/mason-null-ls.nvim#37
williamboman/mason.nvim#722
What should these plugins assume the binary to be called by default:
editorconfig-checker
orec
?The text was updated successfully, but these errors were encountered: