Yosuke Ota comments

Results 557 comments of


                                            Yosuke Ota

Memory leak ??

I think it maybe the fix has been merged but it hasn't been released yet. #10085

feat: add prefer-optional-props-using-with-defaults

EDIT: ~~I misunderstood. Forget this comment.~~ EDIT: Sorry. My previous understanding is correct. I think it would be useful if the rule could check for other cases as well. ---...

feat: add prefer-optional-props-using-with-defaults

Hmm... I think it's a good idea to follow the precedent, but I think the name `require-default-props` can be confusing to report unnecessary defaults. If I had to choose one,...

feat: add prefer-optional-props-using-with-defaults

@neferqiqi can you change this PR?

feat: add prefer-optional-props-using-with-defaults

> but i want to reserve the auto-fix. Because firstly, it only fix the props in current file, so it's safe to auto fix; secondly, for example in my project,...

Rule proposal: `padding-lines-between-tags`

Thank you for the rule proposal. I think it's probably better to be able to set options for each element before and after, like `padding-line-between-statements`. For example, I don't want...

Feature request: vue/match-component-file-name, allow prefixes/suffixes

If you want to control the rules per PATH, you can use the `overrides` configuration. https://eslint.org/docs/user-guide/configuring/configuration-files#how-do-overrides-work

update `no-unused-components` to not mix pascal/camel casing

Thank you for this issue! It would be great if we could catch the cause of the runtime error in advance.

no-unused-components with class-components does not work

No progress has been made on this so far.

Allow disabling file name checking for multi-word-component-names rule

Thank you for posting this issue. If the user enables that option, we should also uncheck the name property as well. However, I think the rules need to check their...