fix: overload methods to know when it should return an array or not #66
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.
Currently, using most methods like:
will make
berry
be of typePokeAPITypes.Berry | PokeAPITypes.Berry[]
, so you must guard it with something like:Typescript allows to overload the declaration of a method so, depending on the parameters, it can infer the return type. This PR makes it so passing
number | string
allows typescript to know the result won't be an array, and passingArray<number | string>
will make it know the result will also be an array.This only works with the
async/await
usage of the package. The callback form is untouched.