Add new vue/prefer-define-component rule#2738
Add new vue/prefer-define-component rule#2738thesheppard wants to merge 5 commits intovuejs:masterfrom
vue/prefer-define-component rule#2738Conversation
absidue
left a comment
There was a problem hiding this comment.
I would suggest reverting all of the formatting changes to the markdown files, as it makes the diff a lot larger than it needs to be, which makes it harder to review.
|
| [vue/padding-line-between-blocks]: ./padding-line-between-blocks.md | ||
| [vue/padding-line-between-tags]: ./padding-line-between-tags.md | ||
| [vue/padding-lines-in-component-definition]: ./padding-lines-in-component-definition.md | ||
| [vue/prefer-define-component]: ./prefer-define-component.md |
There was a problem hiding this comment.
This link definition is now unused. Please run npm run update to regenerate the docs, then both Markdownlint errors should be fixed.
|
I noticed it's been about a month since the last update. Are you still planning to address the formatting feedback and add the changeset? If you're busy or would like help moving this forward, I'd be happy to assist 👍 |
This resolves #2661