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

Playground not working if GraphQL path is set #877

Closed
sgt opened this issue Jun 26, 2019 · 4 comments · Fixed by #984
Closed

Playground not working if GraphQL path is set #877

sgt opened this issue Jun 26, 2019 · 4 comments · Fixed by #984
Assignees
Milestone

Comments

@sgt
Copy link

sgt commented Jun 26, 2019

I don't really get the new PlaygroundOptions logic, but the _pathIsSet variable seems to be always false, and therefore the playground is broken when the path is set manually via options.

            app.UseGraphQL("/g");
            app.UsePlayground(new PlaygroundOptions {QueryPath = "/g"});

When the /playground url is accessed in this setup, 404 is returned.

@michaelstaib michaelstaib added the 🔍 investigate Indicates that an issue or pull request needs more information. label Jun 27, 2019
@michaelstaib michaelstaib added this to the 9.1.0 milestone Jun 27, 2019
@michaelstaib michaelstaib self-assigned this Aug 9, 2019
@michaelstaib michaelstaib added bug and removed 🔍 investigate Indicates that an issue or pull request needs more information. labels Aug 9, 2019
@michaelstaib
Copy link
Member

Hi @sgt,

sorry for the wait. There seems to be a copy paste error here.

I will add some tests and fix the options class.

@michaelstaib
Copy link
Member

You can follow this here #984

@michaelstaib
Copy link
Member

This one is now fixed and will be included into V10 preview 52.

@skmunichetty
Copy link

This worked for me
app.UsePlayground(new PlaygroundOptions { QueryPath = "/graphql", Path = "/playground" });

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants