test: fix issue with new client overriding previously set api key #1305
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.
I was using the tests as informal documentation so I wasn't sure whether to use the
test
or thedoc
tag but since I haven't modified any test output I'm going withdoc
as it applies more closely to how I was interpreting the code.if you call
sgMail.setClient()
before you callsgMail.setApiKey()
then everything is great. If you call them in the order that this test does you'll forever getUnauthorized
401 section withdata.headers
innode_modules/@sendgrid/client/src/classes/client.js
createRequest()
function not includingBearer Authorization <<YOUR_API_KEY>>
This issue is reproducible whether you set the client / key at the top outside of a typescript class, inside the typescript class' constructor, or inside the function right before the
sgMail.send
call.Checklist
Here's a GIF of the issue: