chore: deprecate legacy dynamic route params fully #2801
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.
π Linked issue
β Type of change
π Description
This is actually a breaking change, but we have marked this functionality a deprecated before stable v8 release, so I don't think it should be marked as breaking? π€ I'm not sure..
The deprecation of using
nuxtI18n
withdefinePageMeta
was a bit soft, as we kept using the same key internally forsetI18nParams
I can imagine there may have been users ignoring the warning. So I added a similar warning that should only be logged in a development environment and changed thenuxtI18n
key tonuxtI18nInternal
, this will break the functionality for projects using the deprecated functionality and better communicate that this is an internal key. At some point we may or may not move away from using themeta
key on routes.π Checklist