some configurable way to enable `vue/no-undef-components`

[brc-dd]

Currently using this in some projects:

    'vue/no-undef-components': ['warn', {
      ignorePatterns: [
        'Router(?:View|Link)', // TODO: add nuxt builtins too
        // sefirot builtins - (fundamental mixin, needs update when some new global component is added in sefirot):
        'S(?:Card(?:Block)?|Content|Control(?:ActionBar(?:Button|Close|Collapse)?|ActionMenu|Button|Center|InputSearch|Left|Pagination|Right|Text)?|Desc(?:Avatar|Day|Empty|File|Item|Label|Link|Number|Pill|State|Text)?|Divider|Doc(?:Section)?|Grid(?:Item)?|Head(?:Lead|Title)?|Link|Modal|Trans)',
        // allow specifying additional global components somehow and concat with this array
      ]
    }],

[cuebit]

Since v2 will handle auto imports automagically, what are your thoughts on the scope for implementing auto imports in favour of globals/mixins?

Otherwise, as of v2, we can expose a config in Sefirot directly and merge with project configs since flat configs will simplify this.

[brc-dd]

Hmm, is auto importing based on unplugin-vue-components? We might need to add resolver for sefirot for that 👀 (it should be 3-4 lines though, not much complex). Yeah, we can use auto-imports. It'll be better than writing mixins in sefirot and declaring types manually 👀

@kiaking thoughts 👀

[kiaking]

Yeah while using Nuxt, I'm more comfortable with Auto imports these days 👀 I'm OK with auto imports instead of mixins.

[cuebit]

The entire codebase doesn't necessarily have to be auto imports, though, I think a Nuxt-esque approach of enabled by default would work well.

For Sefirot it would, at the very least, reduce the requirement for mixins/global bootstrapping and, more importantly, provide type awareness which is fundamentally key to this issue.