Builder Deserialization with Type Binding (#921)

[vjkoskela]

Extend support for deserializing via builder if the builder has type bindings by inferring those bindings from the value type. This behavior is not ideal, but addresses the common case, and is controlled by a MapperFeature. This is intended to begin to address the issue described in #921.

[cowtowncoder]

Ok I should get that merged. Just one question: addition of the new method in TypeFactory is probably the only thing I am bit concerned about. I think it's ok to add but could use javadoc.
And a unit test or two that would help document it, too, esp. if testing also done with incompatible case (different number of parameters)?

[vjkoskela]

Apologies for not following up on this sooner. I will add some javadoc and tests as soon as possible. Thanks for taking a look!

[vjkoskela]

Added some javadoc and tests. Let me know how that looks!

[cowtowncoder]

Apologies for slow follow-up here. I think it looks better. I think the only test that could be useful to add would be negative test, to see what happens with incompatible TypeBindings... but not sure how much that can be validated (or if).

[cowtowncoder]

Note: now also backported to 2.12 (to be included in 2.12.0)

[vjkoskela]

Fantastic! Thank you.

[sumannewton]

@cowtowncoder @vjkoskela Is this released? I am waiting for this fix. If not released, when can we expect this?

[cowtowncoder]

@sumannewton As per issue itself, #921 (this is PR), it will be in 2.12.0. 2.12 is still being developed, and will be released "when it's ready": releases are not scheduled on time-basis.
At this point I think that the first release candidate could be released earliest in August, and ideally no later than September. Release usually follows within about a month.
So probably in September/October 2020.