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
[Feature] Allow overriding of qraphiql html #953
Comments
Would be nice, if somebody has a look at my pull request. I want to know if I need to rework something, or if it can be merged. |
I'm currently a bit reluctant to make any changes in the GraphQL implementation at all, since I'd really prefer to eventually drop it from Starlette in favour of someone taking on the workload as a third party package instead. There's a lot of work that's gone into making sure components are really neatly decoupled in Starlette, so it's not a terrible idea to instead copy the GraphQL app into your own codebase, and then make any adjustments from there, rather than holding out for "let's get this changed in core". |
This is understandable, but I still hope it gets merged. Now you have to override the |
Thank you for filing this issue. We have decided to deprecate GraphQL support within Starlette itself so I am going to close this issue. See #619. |
graphiql
uses sources, that are embedded via jsdekivr.net. In some networks hosts like these are prohibited, or there is no internet access at all. On the other side there are several other, enhanced graphql frontends as proposed in #753 or #698A simple approach is to add possibility to overwrite the default graphiql html code.
The text was updated successfully, but these errors were encountered: