GraphQL fields not yet defined

michaelgmcd / vscode-language-babel

VSCode syntax highlighting for today's JavaScript

https://marketplace.visualstudio.com/items?itemName=mgmcdermott.vscode-language-babel

MIT License

131 stars 17 forks source link

GraphQL fields not yet defined #17

Closed lgraziani2712 closed 6 years ago

lgraziani2712 commented 6 years ago

Hello!

I'm having a visual issue:

Since v0.12.0, GraphQL allows "abstract fields", or not yet defined:

Update to match Schema definition language latest specification.

The schema definition language has some slight changes from the original experimental version through the standardization process. New extend forms were added and previously valid forms which omit fields like type Foo {} are now syntax errors and can be replaced with type Foo to indicate that fields are not yet defined.

From: https://github.com/graphql/graphql-js/releases/tag/v0.12.0

Thank you!

michaelgmcd commented 6 years ago

Thanks for using vscode-language-babel! I'm having a little trouble figuring out what your exact issue is. Is it the fact that anotherSchema appears to be giving you an error? That would be a different package causing that (eslint maybe?).

lgraziani2712 commented 6 years ago

Oh! Sorry. I meant the highlightning. It brokes at line 16 because (I think) expects the type Query to have a definition, right?

Since graphql v0.12.0 you can use type Query without defining anything.

The anotherSchema error was linted by eslint, or flow I think, but is not related to the issue.

Thank you for doing this, BTW 😄

michaelgmcd commented 6 years ago

Fixed in latest release