JSON Schema doesn't allow headers for schema

[benkroeger]

Describe the bug
According to the documentation, you can pass headers to a schema url - and the feature itself actually works.
It's just that the provided json schema throws a validation error because it expects schema to either be a string or an array of strings

To Reproduce
set schema to

schema:
  - http://localhost:3000/graphql:
      headers:
        Authorization: foo

yaml schema validation against https://unpkg.com/[email protected]/config-schema.json will report the issue as follows:

Expected behavior
the documented format should be allowed in the json schema

Environment:

• OS: MacOS 11.5.2
• GraphQL Config Version: 4.0.1
• NodeJS: 16.9.1

Additional context

[paleite]

Experiencing the same issue

[Urigo]

Hi @benkroeger and thank you for the report

Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.

It seems already got into stage 1 thanks to your reproduction! Thank you for that!

Now in order to advance to stage 2 we'll need a failing test, would be great if someone could help progress the issues through the stages.

Also we would love to PR to update the schema.

Thank you and sorry that this comment is not a complete solution (yet).

[dimaMachina]

@benkroeger @paleite @zifeo @kevinalh @illarionvk @BasixKOR @frehner @franzwilhelm

Hey guys, sorry for a long time in fixing this problem.
This problem was finally solved in the alpha version [email protected].

I mentioned all of you because you had this problem, so you can test it on your configs, and maybe you have some suggestions for the next major of graphql-config? Please leave it in #626

[BasixKOR]

Note: You can test this by using custom schema options on VS Code YAML extension like this:

"yaml.schemas": {
    "https://unpkg.com/[email protected]/config-schema.json": "graphql.config.*"
}

[dimaMachina]

@BasixKOR thanks, available in [email protected]