Flo Edelmann comments

Results 458 comments of


                                            Flo Edelmann

Removing trailing/leading spaces in directives and bindings

That's formatter (e.g. [Prettier](https://prettier.io/)) territory rather than linter territory. But we currently do have many formatting rules, so this could be considered. @ota-meshi what do you think?

vue/require-toggle-inside-transition - question: should it still be an error with a conditional appear attribute?

> We are using a conditional `appear` attribute so that the animation is not shown on the first load of the app, only when navigating between components. Why not set...

vue/require-toggle-inside-transition - question: should it still be an error with a conditional appear attribute?

Hmm, I'm not sure whether this kind of usage should be encouraged by not reporting an error. @ota-meshi what do you think?

vue/require-toggle-inside-transition - question: should it still be an error with a conditional appear attribute?

Okay, then this is open for contributions. If anyone is interested, a PR is welcome! Please add these test cases: ```vue ```

`vue/require-default-prop` should not trigger when type is `x | undefined` without default value

Related to * https://github.com/vuejs/eslint-plugin-vue/issues/2051 * https://github.com/vuejs/eslint-plugin-vue/issues/2376

`vue/require-default-prop` should not trigger when type is `x | undefined` without default value

I'm not sure if I agree; every optional property (with a `?`) automatically has `| undefined` added to its type, so it would render the rule useless if every optional...

`vue/require-default-prop` should not trigger when type is `x | undefined` without default value

Yes it is. I don't think we can turn that off.

Add autofix to `define-props-declaration`: transform runtime syntax to type-based syntax

PR welcome, but note that the autofix would need to handle quite complex cases like transforming `{ foo: String as PropType, bar: User, baz: Number }` to `{ foo: 'a'...

Update JS env and remove or update parserOptions.ecmaVersion

Will be fixed with #2669 in v10.

`no-setup-props-reactivity-loss` should report template string expressions

Pull request welcome to fix this false-negative!