You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i think the easiest fix might be if autocomplete knows that a key requires quotation, it adds it automatically - afaict the yaml spec allows quoted keys, so i guess they should be supported
not sure what qualifies as requiring quotation but i would guess if the string contains anything non alphanumeric
Describe the bug
(Related to #438 )
I have a schema in which there are conditional extensions based on the value of a property.
If that property starts with
@
and therefore requires to be quoted, autocomplete can bork the schema (or at least further autocompletion")For example, given the following schema:
If the user uses autocomplete to add the
@type
property, the enumerated values are not shown.If the user then goes back and adds the necessary
"
around the key, then the enumerated values are shown, but the autocomplete then borksIf the user adds the full
"@type"
from the outset - ie doesnt use autocomplete, then it works as expectedExpected Behavior
handle keys starting with
@
better/more consistentlyCurrent Behavior
using autocomplete to fill key starting with
@
borks further autocompletionSteps to Reproduce
see above
Environment
The text was updated successfully, but these errors were encountered: