You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You should only get the warning about using v-slot if you are actually using tag or event props
What is actually happening?
Since tag and event have non-falsey default values, the warning will always fire with any use of router-link.
Perhaps you should just compare if the values for tag or event are non-default and fire the warning, even though this doesn't cover the edge case that tag or event are actually being passed in with a value that matches the default.
The text was updated successfully, but these errors were encountered:
closesvuejs#3457
Only show deprecation warning if the props "tag" or "event" are actually passed by the consumer (key exists in propsData), not if they have any value at all (they always have a value since a default is specified in the props definition)
Version
3.5.0
Reproduction link
d2cb951#diff-d69779a774d18aab6696dcf281454982a329104177c1a5f885089da9fefefd94R134-R148
Steps to reproduce
See the conditions for firing the warning:
d2cb951#diff-d69779a774d18aab6696dcf281454982a329104177c1a5f885089da9fefefd94R134-R148
What is expected?
You should only get the warning about using v-slot if you are actually using
tag
orevent
propsWhat is actually happening?
Since
tag
andevent
have non-falsey default values, the warning will always fire with any use of router-link.Perhaps you should just compare if the values for
tag
orevent
are non-default and fire the warning, even though this doesn't cover the edge case thattag
orevent
are actually being passed in with a value that matches the default.The text was updated successfully, but these errors were encountered: