-
Notifications
You must be signed in to change notification settings - Fork 18
Consider removing the @JsonCreator requirement #13
Comments
I have an idea which would apply to
Would this make sense? |
Yes. |
Ok, one more related improvement: FasterXML/jackson-databind#725 which I hope should actually further reduce the need for
a constructor will be used similar to if it was annotated. Cases that do not fall under this would be: a. Multiple visible constructors: no attempt is made to know which one to use; no point guessing as there will always be some cases where determination impossible (same number of arguments, same visibility etc) |
Nice, so after the release the tests should pass. |
I've tried it out locally and tests pass with jackson-databind 2.6.0-SNAPSHOT! |
This issue is solved so I'm closing it. |
Agreed. |
Is release planned soon? |
No immediate plans, but I do hope to start release planning once JsonParser-filtering is implemented for streaming API. The other bigger thing (protobuf dataformat) is complete. |
Does this latest release contain this feature? (jackson-databind) |
2.6.0 has not yet been released, last one was 2.5.3, so not yet. |
This feature would really simplify usage and provide convience for developers.
Considering everyday development techniques I've encountered regarding this issue the most basic use case boils down to:
One additional argument for tackling this issue are value types which will always be immutable.
The text was updated successfully, but these errors were encountered: