Skip to content
This repository has been archived by the owner on Jul 31, 2022. It is now read-only.

Getting errors on local schema file with custom built directives #31

Closed
andres-gr opened this issue Jun 19, 2018 · 4 comments
Closed

Getting errors on local schema file with custom built directives #31

andres-gr opened this issue Jun 19, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@andres-gr
Copy link

I have a custom directive declared in my local schema file, and it is throwing validation errors when used in this file.

[GraphQL: Validation] Unknown directive "withAuth"

screen shot 2018-06-19 at 11 46 36 am

Maybe it's a bug?

Maybe we can have an option in the settings for the extension to declare our own directives or maybe to ignore such errors.

@marktani marktani added the bug Something isn't working label Jun 20, 2018
@divyenduz
Copy link
Collaborator

@andres-gr : Thanks for reporting the issue, I think that extension is not activated for you for some reason as the directive syntax highlighting is not working.

I was not able to reproduce this and it works for me.

Do you see a plug symbol with graphql in your status bar? This signifies that extension is in play.
screen shot 2018-06-25 at 2 39 38 pm

If yes, can you please share a sample repository where this behavior can be observed.

Thanks!

@andres-gr
Copy link
Author

andres-gr commented Jun 25, 2018

@divyenduz thanks for the feedback, I guess I did have something wrong in my .graphqlconfig file as it is now working after doing some changes to that file.

I guess I can close this issue.

@johannpinson
Copy link

Hello @divyenduz

I got the same bug, even if the plugin is running well
capture d ecran 2018-07-18 a 15 53 34

Is the plugin works only with Schema directives (and not directiveResolvers ?)
My actual code follow this example: https://github.com/LawJolla/prisma-auth0-example

Thanks,

@steebchen
Copy link

steebchen commented Aug 16, 2018

I have the same issue. The output tab in VS Code showed some weird errors, and I realized it's because of using a project name with a hyphen:

projects:
  my-project:
    [...]

It works fine for me now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants