[next] feat(Nc*Field): migrate from value to model-value
#4647
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
Signed-off-by: Raimund Schlüßler <raimund.schluessler@mailbox.org>
raimund-schluessler
added
3. to review
raimund-schluessler
requested review from
susnux,
skjnldsv,
Pytal,
ShGKme and
marcoambrosini
raimund-schluessler
changed the title
value to model-value
ShGKme
approved these changes
Oct 13, 2023
Pytal
approved these changes
Oct 13, 2023
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.
☑️ Resolves
This migrates the
Nc*Fieldcomponents to usemodelValueinstead ofvalue. This allows to simply usev-model="text"instead ofv-model:value="text".Depending on what gets merged first, either this PR or #4646 need to be adjusted.