Merged
Conversation
This was really just because this.field should have been this.fields - typo introduced in #11529. But, before I realized that, I simplified to native JS thinking that was part of it. Nope. But keeping the native JS is nice to get rid of a couple of lodash imports.
…do that in Vue 3. Moved the v-for to an outer template.
This was happening because the updated event was being dispatched when anything in the store changed (like preloadedAssets or hidden fields). We only want the event when values are changed.
… the stack when max selections is 1.
…n seem necessary. Fixes error when trying to pick an entry
…closing because it doesnt wait for parent stack to clos.e
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Uh oh!
There was an error while loading. Please reload this page.