Allow auto-complete for object containers with subschemas #391
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
For select properties, it's possible to choose between `v-select` and `v-autocomplete` with the `x-display` option. This makes it possible to do the same for object containers with conditional subschemas.
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.
Hi,
I made a small fix for #361, which I opened some time ago. You recently made it possible to force the
autocompletetag in 490f19f and I would like to have this for conditional subschemas as well. The object container always picks av-selecthere, however. This PR basically let's you pick an autocomplete withx-displayin that class as well.I also removed a redundant line in the select property.
Hope this works for you :)