GraphiQL tweaks
Few suggestions I'd like to make:
-
Change the default
tokenHeaderfromaccess-tokentoAuthorization. I believe the majority of use-cases will be usingAuthorization: Bearer {JWT}. -
Remove the
@Cachefrom the explorer controller. Is this really needed for dev? -
Change the route path to something that doesn't start with
/graphql. I have/graphqlbehind a firewall pattern, which then blocks the explorer too. I've since changed the path to/_graphiqlto match other dev related tools (eg._profiler) -
Make the explorer a dedicated bundle that can added to the
AppKernelbased on environment (eg.DebugBundleandWebProfilerBundle).
Hi @bjunc,
I would like to add some notes:
- Let's make it as config parameter (of new budle).
- Yes, you can easily remove it, it's not necessary any more.
- Yes too.
- Absolutely yes. It would be great to add here else one extension for graphql Altair.
Sounds great! @portey what are the next steps?