Auto-completion on sub-objects doesn't work about vscode-yaml HOT 8 CLOSED

I'm working on adding this now. I think I was just confused as I haven't seen that before

from vscode-yaml.

It should be ready in the next few days!

from vscode-yaml.

@schickling We just updated the extension with a brand new autocompletor! It now fixes this issue and does autocompletion on values in the schema as well!

from vscode-yaml.

Out of curiosity is sub_field a child node of some_dynamic_key and some_dynamic_key a child node of my_other_root_field? If this is the case then it looks to be a bug. The autocompletion was built to be context dependent so as long as some_dynamic_key is a child of my_other_root_field then it should autocomplete with sub_field.

Heres a demo of how it should behave:

(I used http://json.schemastore.org/swagger-2.0 as my schema)

from vscode-yaml.

What you've posted seems to work for me but here is what doesn't work for me:

    "yaml.schemas": {
        "https://raw.githubusercontent.com/graphcool/graphcool-json-schema/master/src/schema.json": "graphcool.yml"
    },

from vscode-yaml.

At the current time the auto completion is context dependent only. Since some_name isn't a child of functions we won't be able to autocomplete anything under some_name. Additionally, auto completion is provided for results that are valid according to the schema, since some_name isn't valid in the schema as far as I can see it wouldn't autocomplete on that either.

from vscode-yaml.

I'm not sure why you think it's not valid? As you can see here in the definition functions is of type: object which should allow for arbitrary keys. The values however are of type: #/definitions/function.

So either we've misunderstood JSON schema or this seems like something this plugin should support 🙂

from vscode-yaml.

It's awesome that you're working on this. Is there any rough eta?

from vscode-yaml.