-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Implement JsonParser.getNumberTypeFP()
for binary backends
#443
Comments
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 6, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 7, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 7, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 7, 2024
cowtowncoder
added a commit
that referenced
this issue
Jan 7, 2024
Completed, merged to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that FasterXML/jackson-core#1149 has been implemented and there is base implementation of
getNumberTypeFP()
inJsonParser
(which basically just returns "unknown" in all cases), it is necessary to override this for binary formats that have specific types (Avro, CBOR, Ion, Protobuf, Smile all do, I think) to report true underlying type.This will allow achieving good balance between somewhat clashing goals of:
Object
,JsonNode
,Number
target types)To do that, binary backends should expose true types.
The text was updated successfully, but these errors were encountered: