Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow case insensitive deserialization of String value into `boolean`/`Boolean` (esp for Excel)

See original GitHub issue

At the moment, com.fasterxml.jackson.databind.deser.std.NumberDeserializers.BooleanDeserializer#_parseBoolean support only "true" and "True" (and the same for false) but fails for values like "TRUE" It would be great to do the matching case insensitive out of the box (similar to how java.lang.Boolean#parseBoolean checks for true)

Issue Analytics

State:
Created 6 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

remalcommented, Sep 7, 2018

I’ve sent a PR for the issue: https://github.com/FasterXML/jackson-databind/pull/2132

0reactions

cowtowncodercommented, Jun 25, 2020

Ended up re-thinking this and simple also allowing “TRUE” and “FALSE” at this point.

Some further thoughts:

With 2.12, CoercionConfigs will dictate if “Boolean from String value” itself is allowed at all (and can be easily prevented)
If more granular control over “but which String values” needed, two main approaches: for most advanced, custom deserializer suggested; but if case-insensitive was still desired, could then use strict/lenient setting – however, not sure there will be need for that.