Set MaxInt to 51 as the existing logic isn't inclusive #46
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.
Closes #45
Sets MaxInt to 51 as existing logic isn't inclusive
Problem
Currently if you pass through 50 on methods which have limit?: MaxInt<50>, you get a typescript error saying that you can only do 0-49. On the Spotify API/Documentation, 50 is allowed so this should be fixed to allow it to be inclusive of the number set.
Solution
Set the MaxInt to 51, without changing the underlying logic.
Side note for reviewer
I tried changing the existing logic for MaxInt (existing logic below)
But, I don't have the best Typescript knowledge, so I couldn't work out a way to make this inclusive - I believe it's an open discussion on Typescript issues for making this nicer to do microsoft/TypeScript#54925 So setting these to MaxInt<51> was a bit of a compromise to make this work. Maybe someone else has a nicer way to fix MaxInt/_range