Error Handling for null Params to Client.prototype.query() #1651
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.
Add's a basic assertion to
Client.prototype.query()
ensuring thatconfig
is notnull
orundefined
. This fixes #628 — which was closed, but the behavior described in that issue lives on. I added some additional tests around the new logic.I ran into the same problem described in that issue — some bad destructing logic on my end led to
config
beingundefined
when callingquery()
. That results in aTypeError
when thetypeof config.submit === 'function'
assertion is executed. The behavior is still basically the same, except that the error is detected, described, and sent to the userscallback
orPromise.reject
ed.