Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Hex number as an entry of an Object causing problem(s) with binding to POJO #71

Closed
cowtowncoder opened this issue Feb 12, 2018 · 3 comments
Closed

Hex number as an entry of an Object causing problem(s) with binding to POJO #71

cowtowncoder opened this issue Feb 12, 2018 · 3 comments
Labels
has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue yaml Issue related to YAML format backend
Milestone
2.12.0

Comments

@cowtowncoder
Copy link
Member

It looks as if content like:

prop:
  subs:
     more: text
id: 0x1962

causes problems due to coercion (or not?) as a hex-number.
@cowtowncoder cowtowncoder added the yaml Issue related to YAML format backend label Feb 12, 2018
@asomov
Copy link
Contributor

asomov commented Mar 8, 2018

yes, this HEX number according to YAML 1.1

@cowtowncoder cowtowncoder added good first issue Issue that seems easy to resolve and is likely a good candidate for contributors new to project 2.12 and removed active labels Sep 18, 2020
cowtowncoder added a commit that referenced this issue Nov 22, 2020
@cowtowncoder
Add (failing) tests for #25 and #71
da1982e
@cowtowncoder cowtowncoder added the has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue label Nov 22, 2020
@cowtowncoder cowtowncoder mentioned this issue Nov 22, 2020
Closed
@cowtowncoder cowtowncoder removed the good first issue Issue that seems easy to resolve and is likely a good candidate for contributors new to project label Nov 23, 2020
@cowtowncoder cowtowncoder added this to the 2.12.0 milestone Nov 23, 2020
@cowtowncoder cowtowncoder mentioned this issue Nov 23, 2020
Closed
cowtowncoder added a commit that referenced this issue Nov 23, 2020
@cowtowncoder
Fix #71 and #233 (support for binary, octal, hex numbers)
7ca2baa
cowtowncoder added a commit that referenced this issue Nov 23, 2020
@cowtowncoder
move #71 test to non-failing to guard against regression
0a5d833
cowtowncoder added a commit that referenced this issue Nov 23, 2020
@cowtowncoder
... but need to move tests for #71 back under failing for 3.x due to …
69ec7d0 
…diff in yaml engine
@asomov
Copy link
Contributor

asomov commented Nov 24, 2020

@cowtowncoder please be aware that in SnakeYAML Engine (and YAML 1.2) this is no HEX number by default.

@cowtowncoder
Copy link
Member Author

@asomov Yes, correct. Thank you for confirming; I thought this was the case wrt earlier discussions.

That will affect 3.0, plans. Not sure what to do there, I may want to file separate issues for question(s) regarding 3.0.

@rohanKanojia rohanKanojia mentioned this issue Jul 17, 2024
Merged
11 tasks
@manusa manusa mentioned this issue Jul 18, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
has-failing-test Indicates that there exists a test case (under `failing/`) to reproduce the issue yaml Issue related to YAML format backend
Projects
None yet
Milestone
2.12.0
Development

No branches or pull requests
2 participants
@cowtowncoder @asomov