Resolve Vue compiler warnings after upgrade to 3.5 #13279
Merged
+53
−45
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.
Summary
This resolves Vue compiler warnings that started appearing after the upgrade to Vue 3.5.
Fixes #13124
Occurred changes and/or fixed issues
Technical notes summary
It appears that this is a behavior that was introduced in to vuejs/core#12088. There's some debate as to whether or not the message is always valid, but it appeared simple enough for us to update our table usage to resolve the warning and clean up the console output.
Areas or cases that should be tested
The affected tables should be reviewed for regressions:
Areas which could experience regressions
The affected tables should be reviewed for regressions:
Checklist