Improve error range for vue/max-props
#2532
Merged
Conversation
This file contains hidden or 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
FloEdelmann
approved these changes
Aug 20, 2024
Member
FloEdelmann
left a comment
FloEdelmann
left a comment
There was a problem hiding this comment.
Makes sense, thank you! 🙂
FYI @ota-meshi: I'm going to merge this without your review because this is such a small uncontroversial change.
FloEdelmann
changed the title
vue/max-props
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
While trying out the new unreleased props rule, I noticed that the rule only highlights the very first prop if violated, instead of the entire props block. I think this is slightly confusing.
Therefore I changed it to report the parent node and therefore the entire props block.