New rule: no-submodule-imports

[adidahiya]

I'd like a new rule to disallow reaching into submodules in import paths. Similar to eslint-plugin-import/no-internal-modules (but we can't call it that since TypeScript has its own notion of "internal module").

// bad
import { Keys } from "@blueprintjs/core/dist/common";

// good
import { Keys } from "@blueprintjs/core";

with rule config

"no-submodule-imports": {
  "options": [
    "@blueprinjs/core"
  ]
}

[aervin]

Will this be very similar to the "import-blacklist" rule? If so, I think I could give it a try.

[ajafff]

Yes, this rule will be very similar to import-blacklist. In fact there will only be a different condition to show an error. The rest of the logic can be exactly the same. Am 02.08.2017 18:07 schrieb "aervin_" <notifications@github.com>: Will this be very similar to the "import-blacklist" rule? If so, I think I could give it a try. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3051 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaeKA9jQXoNA-Pn-8gAS91bzWxf-8JIks5sUJ7EgaJpZM4ObgWg> .