Configure graphql path

[poulad]

Following #6

This is not the best approach but easiest for clients to use.

Here is what happens if GraphQL url is not the default (as set in index.html):

• Create a temp dir /tmp/graphiql-dotnet/graphql-path.js
• Write var graphqlPath='/api/graphql';
• Serve it as file
• index.html loads the file and path is set

[josephwoodward]

Oh awesome, thanks for this.

I'm wondering if it's worth seeing if we can avoid writing to disk bypass any drive permissions issues etc. I wonder how feasible it would be to make it an in memory JS files (given the size of it too)?

[poulad]

I'll see if I can implement IFileProvider for that.

[josephwoodward]

Thinking more about the benefits of storing it in memory over on disk is if someone removed the library, the files go with it (instead of leaving temp files on disk).

One way to do it would be to register an HTTP endpoint (where the user defines the endpoint) as middleware that reads the js file from the file provider/assembly and returns it as a stream.

[OlegZee]

This if vital PR, guys. I'd separate the issues.
@pouladpld, consider passing parameter via query parameter so that there's no need to update index.html and take care on caching the file.

[rickhopkins]

This would be a great fix to have in place.

[josephwoodward]

Keen to pick this one back up and get it sorted in the next couple of days.

[josephwoodward]

Almost finished on this, watch this space.

[josephwoodward]

Got an open PR for this (#23) with a few changes. Was keen not to write to disk so instead have a mapped path that returns the small JS file.