-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
InvalidOperationException when visiting GraphQL explorer #15304
Comments
@lampersky can you please pull the latest from main or use the latest previews and see if this is still an issue for you? |
@MikeAlhayek same issue with latest changes from main: |
I'll leave this to @hyzx86. I can't reproduce this issue on the main branch (tried existing site and create new site.) Is this issue from the main branch or your project? If you are running your project, can you make sure you are not adding this into your project manually?
Also, search your project for any code that uses I am also wondering if you have weird dependency that could be causing registering OrchardCore/src/OrchardCore/OrchardCore.Apis.GraphQL.Abstractions/ServiceCollectionExtensions.cs Lines 17 to 40 in a8bdd63
|
@MikeAlhayek I'm using |
Strange. Do you know if you are using a default recipe? I can't seems to reproduce the issue which is strange. I tried the blog recipe and enabled the GraphQL feature. |
@MikeAlhayek did you try to reconfigure existing ContentPart? and then go to GraphQL editor? I'm using Blank recipe with GraphQL enabled. |
Thanks I was able to reproduce. Check out the referenced PR if you have time to test it out. |
@MikeAlhayek couldn't repro, what exactly did you do? |
First you have to visit the GraphiQL. Then edit any content type "like the articles content type". Then refresh GraphiQL page again and you should encounter the issue. |
I've just updated to the latest OC and getting this when visiting GraphiQL explorer:
Steps to reproduce:
I've just checked, and it looks like you don't need to create new ContentType, you can reconfigure existing one instead. This way you could also reproduce the issue.
The text was updated successfully, but these errors were encountered: