-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Consider another package name? lint? linter? source_lint? #57171
Comments
Our friends in naming would probably like "Linter for Dart". |
👍 for "Linter for Dart" for the human-readable/product name, but what about the package name? Is "linter" too open-ended? |
For the record, we also have package name "linter" is fine, because it's scoped to pub.dartlang.org Formal project name: "Linter for Dart" is great. Repo name: linter, because it's scoped to dart-lang Org |
+1! On Thu, Feb 12, 2015 at 10:45 AM, Seth Ladd [email protected]
|
Works for me. @sethladd : can you do the move? I'm guessing/hoping history, issues, etc will make the transition? |
Is this package going to expose a command-line app? If so, I find it nice to have the name of the command-line app match that of the package, and 'linter' wouldn't be a great name for a command-line app. Just something to consider. |
Absolutely. I've got a provisional commandline entry point already. Thanks for chiming in @seaneagan! |
Go ahead and rename this repo. GitHub is very good at redirects. and yes, matching command-line names is generally a good idea. |
Besides a command-line app, another place where namespacing with |
Rename done. That said, @seaneagan, you bring up some good points. Let's take the config file conversation over to #57153... |
dart_
is a bit redundant.CC @sethladd for his perspective
The text was updated successfully, but these errors were encountered: