Consider another package name? lint? linter? source_lint?

[kevmoo]

dart_ is a bit redundant.

CC @sethladd for his perspective

[sethladd]

Our friends in naming would probably like "Linter for Dart".

[pq]

👍 for "Linter for Dart" for the human-readable/product name, but what about the package name? Is "linter" too open-ended?

[sethladd]

For the record, we also have dart_style in our Org.

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

[kevmoo]

+1!

On Thu, Feb 12, 2015 at 10:45 AM, Seth Ladd notifications@github.com
wrote:

For the record, we also have dart_style in our Org.

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

—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/dart_lint/issues/25#issuecomment-74127398.

[pq]

Works for me. @sethladd : can you do the move? I'm guessing/hoping history, issues, etc will make the transition?

[seaneagan]

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.

[pq]

Absolutely. I've got a provisional commandline entry point already. Thanks for chiming in @seaneagan!

[sethladd]

Go ahead and rename this repo. GitHub is very good at redirects.

and yes, matching command-line names is generally a good idea.

[seaneagan]

Besides a command-line app, another place where namespacing with dart or dart_ would come in handy be #57153. The configuration file should be namespaced e.g. .dartlintrc instead of .linterrc, and it's much easier to mentally connect that to a dartlint or dart_lint package than a linter package.

[pq]

Rename done. That said, @seaneagan, you bring up some good points. Let's take the config file conversation over to #57153...