Is there anyway currently (or would it be hard to implement) to have the schema pulled via URL saved into the schema file? My problem is that my graphql endpoint requires authentication (api token) the expires every hour. This means that if I check out my code in a new location I need to grab a new token and plop it down in the headers in the config file so that the plugin stops complaining about my queries not being valid.
I can write a script to grab a token and throw it into the config file (for when my schema changes) but I would love it if when you first checkout code it would use the last fetched (and committed to git) schema.
Is there anyway currently (or would it be hard to implement) to have the schema pulled via URL saved into the schema file? My problem is that my graphql endpoint requires authentication (api token) the expires every hour. This means that if I check out my code in a new location I need to grab a new token and plop it down in the headers in the config file so that the plugin stops complaining about my queries not being valid.
I can write a script to grab a token and throw it into the config file (for when my schema changes) but I would love it if when you first checkout code it would use the last fetched (and committed to git) schema.