Scope naming for kt_jvm intermediate targets

[sugarmanz]

Release Notes

If the target name is the same as the local package name, the generated targets will omit the names.

Regular scope naming strategy:

# path/to/module-a/BUILD
kt_jvm(name = "module-a-sub-lib")

Generates linting targets against module-a-sub-lib:

//path/to/module-a:module-a-sub-lib-lint
//path/to/module-a:module-a-sub-lib-lint-fix

Optimized scope naming strategy:

# path/to/module-a/BUILD
kt_jvm(name = "module-a")

Generates linting targets against module-a-sub-lib:

//path/to/module-a:lint
//path/to/module-a:lint-fix

[adierkens]

Seems reasonable. Might be worth following the same convention in the JS rules too.

With scoped package names (@foo/bar) the local package name won't ever match though which can be pretty annoying.

[sugarmanz]

@adierkens would it be worth changing the target name vs NPM package name strategy to make that a bit more convenient?

[intuit-svc]

🚀 PR was released in v0.4.0 🚀