You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue also now affects master branch but not the 2.15 branch.
Scala 2.13 is less affected than Scala 2.11/2.12 and Scala 3. The classes generated by Scala 2.13 compiler may not expose the wildcards. The deserialization issues affect types like Either[_, String] - in this case the user expects the result to be a Right so they don't provide an explicit type for the Left. This is a real edge case and something that I wouldn't encourage users to do. We have tests that do this but it was probably just a convenience for the person writing the tests.
The text was updated successfully, but these errors were encountered:
pjfanning
changed the title
2.16 jackson-databind deserializtion changes have broken support for the scala.util.Either class
2.16 jackson-databind deserialization changes have broken support for the scala.util.Either class
Oct 7, 2023
see FasterXML/jackson-databind#4147
https://github.com/FasterXML/jackson-module-scala/actions/runs/6442522651/job/17493416303
The issue also now affects master branch but not the 2.15 branch.
Scala 2.13 is less affected than Scala 2.11/2.12 and Scala 3. The classes generated by Scala 2.13 compiler may not expose the wildcards. The deserialization issues affect types like
Either[_, String]
- in this case the user expects the result to be aRight
so they don't provide an explicit type for theLeft
. This is a real edge case and something that I wouldn't encourage users to do. We have tests that do this but it was probably just a convenience for the person writing the tests.The text was updated successfully, but these errors were encountered: