fix: SDK crash on conversion of double type range values to long type

TobiasPott commented 3 years ago

This pull request targets the issue of values retrieved from parse-server exceeding the long64 value range mentioned in #339 It handles it by using a fallback to the double type with a higher range as this also would be the type with which the higher values can only be added to the parse-server using the .NET SDK.

It also includes a test checking for long max and min values and the double max and min values and the specific value mentioned in the issue.

@TheFanatr Could you take a look at this PR and give me feedback whether or not to change anything (especially the test part as I'm unsure if it will be sufficient)

saamerm commented 2 years ago

@TheFanatr @TobiasPott any update on this?

parse-github-assistant[bot] commented 3 months ago

Thanks for opening this pull request!

❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

parseplatformorg commented 3 months ago

🎉 This change has been released in version 3.0.1

parse-community / Parse-SDK-dotNET

fix: SDK crash on conversion of double type range values to long type #342

Thanks for opening this pull request!