Add vue/no-undef-properties rule
#1472
Merged
+1,877
−43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ota-meshi
force-pushed
the
no-undef
branch
2 times, most recently
from
ea0248f
to
65111b4
Compare
ota-meshi
force-pushed
the
no-undef
branch
2 times, most recently
from
251dfdf
to
c6c7cee
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
vue/no-undef-propertiesrule.vue/no-undef-propertiesrule warns of using undefined properties.close #875
This rule is a slightly modified version of the rule used by the company I belong to.I don't know if this rule can be used in general because it gives a lot of false positives when using
mixinsetc.If you want to try this rule, could you copy the source code from this PR and try it.
I would appreciate it if you could give us your opinion on the results you have tried.
I think support for
<script setup>will help many users.