-
Notifications
You must be signed in to change notification settings - Fork 326
[Breaking graphiql Bug] Cannot load graphiql with new resource location #83
Comments
similar issue. I remapped graphiql to /app/graphiql as allowed by the framework. The page will not load because the resource paths are hard coded. |
@apottere any update on if you have seen the same problem? |
@rwilliams-r7 Maybe you can create a pull request with the fix you suggested? |
Actually just removing the dots will suffice: <script src="/vendor/es6-promise.auto.min.js"></script>
<script src="/vendor/fetch.min.js"></script>
<script src="/vendor/react.min.js"></script>
<script src="/vendor/react-dom.min.js"></script>
<link rel="stylesheet" href="/vendor/graphiql.min.css" />
<script src="/vendor/graphiql.min.js"></script> I'll change it. |
This seems to happen still. My dependency versions are
|
@liangjacky These artifacts have moved to another groupId with version 5.0.3: |
still reproduces..any solution?
|
this was a problem for me and for some reason it doesn't work unless i create a bean that extends what i ended up doing is using the CDN option via the graphql:
playground:
cdn:
enabled: true
version: 1.7.20 this obviously serves up the static resources from the CDN, but it should suffice for my use. |
I have solved graphiql and voyager with WebMvcConfigurer below code:
|
New resource location does not load within graphiql.html. Reference's seem to need to be updated to
Without this change the graphiql page does not load.
The text was updated successfully, but these errors were encountered: