Negative numbers not quoted correctly wrt `ALWAYS_QUOTE_NUMBERS_AS_STRINGS`
See original GitHub issueWhen initializing a YamlFactory
as follows, negative numbers are not quoted correctly.
YAMLFactory factory = new YAMLFactory();
factory.enable(YAMLGenerator.Feature.MINIMIZE_QUOTES);
factory.enable(YAMLGenerator.Feature.ALWAYS_QUOTE_NUMBERS_AS_STRINGS);
Serializing 60
currently results in "60"
.
Serializing -14
currently results in 14
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Negative numbers aren't showing with parentheses in Excel
Negative numbers not showing with parentheses? This article will explain how to fix this problem in Windows 10.
Read more >Negative Numbers in Excel
Negative numbers are typed into Excel by using a hyphen - symbol and the number. Example: negative 3 is typed “-3†without the...
Read more >Why can't R handle inequalities between negative numbers in ...
A "number in quotes" is not a number at all, it is a string of characters. Those characters happen to be displayed with...
Read more >We have a decimal field created that contains negative ...
In the Classic UI the field sorts correctly showing negative numbers smaller than their counterparts. In the new UI the sort does not...
Read more >Quote Line Editor does not show negative ... - Salesforce CPQ
In CPQ Version 220 with multi-currency enabled currency fields will not display negative values correctly- instead they will show as positive.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@dpbevin Thank you very much for reporting this, contributing fix! Backported in 2.10 so it’ll be in 2.10.4 as well as 2.11.0.
@dpbevin that’s perfectly fine, I should have waited couple of minutes 😃
(just happened to go through my email when notification just arrived)