This repository was archived by the owner on Mar 20, 2023. It is now read-only. 
  Add option to load graphiql files locally #219
   Closed  
   Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.    
 
An implementation of #112, allows a user to pass "local" or "cdn" to the graphiql option in order to specify where the files should be loaded from. Is also compatible with true/false, defaulting to "cdn" if true.
I put the files in a new folder called vendor, but I am happy to change it to work a different way (using the files from npm for example), if that would be better.
I've not used flowtype before so I hope I have covered everything there! And no tests or documentation changes yet, but I can also look into adding them!
Note: I have had to change what is returned by the graphqlHTTP function, it now returns an express router instead of just a middleware function, this is so the vendor files can be served using express.static under the same route as the graphql endpoint