Rafał Pitoń
Rafał Pitoń
Looks like this would be resolved if we supported custom query parser option, eg: ```python class AllowedQueriesParser: ... allowed_queries_parser = AllowedQueriesParser( allowed_queries={ "GetUsers": gql( """ query GetUsers { users {...
Punting this for Ariadne 0.17, but I'll open separate issue for configurable parsers.
I agree, we could raise an error when this happens!
I've tagged this as decision needed because GraphiQL is still behind Playground.
My plan for this is to have an option on `GraphQL` app named `explorer`. If this is set to `None`, we'll use whatever is default GraphQL explorer for Ariadne at...
Looks nice, @davlee1972. Is that version of GraphiQL available on CDN? We don't want to maintain and serve custom API explorer builds for Ariadne.
> But the Explorer functionality is a plug-in.. The YouTube video above goes through the plug-in installation steps. I understand, but Ariadne never served any static files for API explorers,...
After some experimentation (and having to implement custom template engine) I've got this:  So explorers are strategy objects, and each explorer is free...
I'm not sure we can do that in Ariadne core, seeing how Apollo keeps client part of their product, and there's no mention anywhere about running IDE on your own...
Perfect, this is what I was looking for!