Closed simPod closed 2 years ago
Hi! Are there any errors containing the "GraphQL" string in the log Help -> Open log in ...
?
You can also try to run it from the configuration file using this green button:
I tried also the green button but the result was the same. Will try to check the logs tmrw, thank you for reply.
I'll look through the code to check it again.
Also, please, try to remove the schema file explicitly and introspect it again. Now it's possible that the newly introspected schema in not opened in the editor, but an introspection was successful. To open the editor should be a default behavior, but something could go wrong. It's configured by this new option:
Can be related #520. Workaround if NullPointerException
is present https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/issues/520#issuecomment-989048076.
Yup, I have that checked.
Clicking on green arrow does not produce any exception.
There was this inspection when IDE started
java.lang.NullPointerException
at com.intellij.lang.jsgraphql.ide.introspection.GraphQLIntrospectionService.getSecurityConfig(GraphQLIntrospectionService.java:198)
at com.intellij.lang.jsgraphql.ide.introspection.GraphQLIntrospectionService$IntrospectionQueryTask.run(GraphQLIntrospectionService.java:537)
at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:436)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:120)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:496)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:244)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:624)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698)
at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:623)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:66)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:244)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:829)```
Should be fixed in 3.1.2.
Confirmed, it works. Thanks!
I'll look through the code to check it again.
Also, please, try to remove the schema file explicitly and introspect it again. Now it's possible that the newly introspected schema in not opened in the editor, but an introspection was successful. To open the editor should be a default behavior, but something could go wrong. It's configured by this new option:
This is really helpful, specially if you use a keyboard shortcut I was desperately looking for this
Describe the bug
Running introspection does nothing. It does not seem to issue any request nor gives any error
To Reproduce
Introspected
a
:Version and Environment Details Operation system: [version] IDE name and version: 2021.3 IDEA Plugin version: 3.1.0