Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphql enpoint unable to fetch schema #623

Open
eb0687 opened this issue Dec 31, 2024 · 1 comment
Open

Graphql enpoint unable to fetch schema #623

eb0687 opened this issue Dec 31, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@eb0687
Copy link

eb0687 commented Dec 31, 2024

Describe the bug
When querying the graphql endpoint using insomnia I am able to see the response, however I get a warning that I am unable to fetch the schema:

Insomnia_iKWIafgAuq

when reviewing the debug console of insomnia i get the below error as well:

Error: Introspection must provide input type for arguments, but received: [FirewallScheduleTimeRange]!.

Due to the above problem I do not get autocomplete in insomnia when writing queries as insomnia is unable to fetch the data in the schema at all.

To Reproduce
Steps to reproduce the behavior:

  • install insomnia
  • get the jwt token via the /api/v2/auth/jwt endpoint
  • query the graphql endpoint on /api/v2/graphql
  • response of 200 successful
  • but warning saying unable to fetch schema due to the error specified above

Expected behavior
When querying the endpoint I expect autocomplete in insomnia, this is only possible if the documentation is populated if fetching from the schema is successful.

pfSense Version & Package Version:

  • pfSense Version: 2.72
  • Package Version v2.3.0

Affected Endpoints:

  • URL: /api/v2/graphql

Additional context

@jaredhendrickson13
Copy link
Owner

Seems there are some object types being mixed up somewhere when the schema is being generated. I'll get working on a fix for this. Assuming the fix doesn't require significant changes I can likely have it in the next patch. Otherwise, I'd expect it in v2.4.0.

Thanks for reporting this!

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

No branches or pull requests

2 participants