I’ve never really been a fan of APIs that have a dual pair of methods: new ObjectMapper().treeToValue(tree); new ObjectMapper().uncheckedTreeToValue(tree);
but they can serve a purpose in situations like this. It does start to get rather verbose/wordy tho. If 3.0 is going to have a much larger exception rewrite, for those who want the relaxed behaviour now - would such a compromise be acceptable? Mark From: Tatu Saloranta <[email protected]> <[email protected]> Reply: [email protected] <[email protected]> <[email protected]> Date: 13 October 2020 at 5:15:08 AM To: [email protected] <[email protected]> <[email protected]> Subject: [jackson-dev] Reverting source-incompatible change in 2.12 (ObjectMapper.treeToValue()) I am leaning towards reverting the change from 2.x and leaving for 3.0 (where there will be bigger exception rewrite anyway) but thought I'd ask if anyone has other arguments to make in favor of incremental 2.x changes, even at expense of some compatibility issues. -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CALYGm1xtvLOh7h1mXEh_fhwy6eX2mX2szT1Er4Q%2BDCvej9tG3Q%40mail.gmail.com.
