fix(ui): use the correct collection when saving in AddNewRelation #14836
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.
What?
Currently when you use the create button in a relationship field that has more than one collection in its
relationToand a collection that isn't first in the list is selected, the selected value in the field will always be pointing to the first collection in the list, causing incorrect results or validation errors.Why?
The selected value in the field should be applied to the collection the user has selected, not just the first collection in the
relationToarray.How?
Use the selected collection in the
onChangehandler instead ofrelatedCollections[0].Fixes: #14728