Flo Edelmann

Looks good to me :slightly_smiling_face: Please go ahead and adjust the docs now :wink:

And could you also add the same option to [`vue/singleline-html-element-content-newline`](https://eslint.vuejs.org/rules/singleline-html-element-content-newline.html) as well please?

> I'm not sure why it's required to test `elem.children.length === 0` _and_ `getFirstTokensBetween().length === 0` Probably it is indeed not needed, seems like both were added at the same...

It seems that the simple fix is also not working correctly for `multiline-html-element-content-newline`, see https://deploy-preview-2581--eslint-plugin-vue.netlify.app/rules/multiline-html-element-content-newline.html#ignorecomments-true: ```vue content ``` So apparently a more elaborate logic is needed after all, probably that...

Adding that to the naive config in my post above leads to the same error for the `consistent-type-assertions` rule, which does not require type information. So only disabling type-aware rules...

I didn't expect this little feature request to split into three sub-issues :sweat_smile: 1. allow ESLint to isolate a language or glob from the rest of the config 2. FAQ...

# Export files validity (Output of test script `tests/github/exports-valid.js`.) Test the exported files of selected fixtures against the plugins' export tests. You can run a plugin's export tests by executing:...

Done: https://github.com/openstreetmap/id-tagging-schema/pull/1817

# Export files validity (Output of test script `tests/github/exports-valid.js`.) Test the exported files of selected fixtures against the plugins' export tests. You can run a plugin's export tests by executing:...

Thanks Benjamin Blaikner and @kengruven!