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.
Changes that were applied:
migrations.json
as unknown
toupdateOptions
to fix a previously working type conversionskipToken
check tonormalizeOptions
to narrow down typingPR Checklist
Please check if your PR fulfills the following requirements:
No addidtional changes were made
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #199
What is the new behavior?
Does this PR introduce a breaking change?
Other information
There is a type conversion that previously was working in
updateOptions
, now i addedas unknown
to it to make it work again. Linting and testing did work out of the box, so no changes were made here. Only building had the error on top and theskipToken
check, since now thequeryFn
has aunique symbol
as additional type on it, for that reason i added the check on it to filter out the symbol and return the default options. So maybe it would be good if you can check what i did @NetanelBasal and if everything checks out to your liking