-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FIX] Issue #202 and #190 #206
base: master
Are you sure you want to change the base?
Conversation
@@ -303,7 +303,7 @@ func TestUnmarshalSetsID(t *testing.T) { | |||
t.Fatal(err) | |||
} | |||
|
|||
if out.ID != 2 { | |||
if out.ID != 9223372036854775807 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we used this value previously, the test would fail;
@aren55555 lmk what you think. |
@@ -495,27 +498,26 @@ func handleTime(attribute interface{}, args []string, fieldValue reflect.Value) | |||
return reflect.ValueOf(t), nil | |||
} | |||
|
|||
var at int64 | |||
switch v.Interface().(type) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original logic was kept, since we're still checking the type of the attribute
, while the previous/following checks are done to the fieldValue
kind.
I wonder if we should check the fieldValue
kind here as well for consistency.
I'll take a look on Sunday when I'll actually be able to allocate enough time to dig into this. |
… the handleStruct() function
@aren55555 the work on this PR is done, do take a look. |
@aren55555 would be nice if you can merge according the dependency to #122 |
Description
This pull request aims to fix numeric precision when decoding, fixing issue #202 and potentially #190 and #120?
Task items:
UseNumber()
;handleNumeric()
function);