Point Precision not getting marshaled correctly... #2093
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…shaled correctly??
|
Thanks @derailed -- looks like a bug to me. @corylanou ? @derailed -- can you sign the CLA, so we can merge this? |
|
@corylanou -- CLA has been signed. +1 from me. Please merge if it makes sense to you. |
corylanou
added a commit
that referenced
this pull request
Mar 28, 2015
Point Precision not getting marshaled correctly...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not sure if this is a bug or was intended as such. Ran into the use case while marsh/unmarsh a slice of client.Point. I was loosing the points precision during the marsh operation.
Corrected client code and associated test and ran tests successfully.