Refactor creation of headers

[chrisbuttery]

This PR refactors how headers are created.

I found the existing method cause Authorization errors regardless if the dashboard URL was public, or was protected and a token was provided.

// This is the response from an 'open' URL

Error: Not Authorised!: {"response":{"errors":[{"message":"Not Authorised!","locations":[{"line":2,"column":11}],"path  ":["pages"]}],"data":null,"status":500},"request":{"query":"{\n          pages {\n            id\n            title\n            }\n        }"}}

// This is the response from a 'protected' URL with a token provided

TypeError: Cannot read property '1' of null


This proposed change only includes headers keys if their values are provided.

[Redmega]

Interesting, I didn't face those issues when using public or private endpoints. It may be something related to the new GraphCMS beta? Or I'm wondering if it's something platform specific? What OS / version are you on?

In any case, code looks fine. I'll do some testing tonight get it merged.

[chrisbuttery]

@Redmega These points have been addressed. Let me know if you require anything else. 👍

[Redmega]

Deployed as v1.0.0-alpha.3!

[github-actions[bot]]

:tada: This PR is included in version 0.1.0-next.1 :tada:

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: