FasterXML / FasterXML/jackson-core
Explicitly indicate Nullability of arguments and return values (JSpecify) -- for 3.3?
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 928
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 24
Description
Currently `nullability` is not explicitly stated for `Jackson`.
On the other hand, there are actually APIs that do not allow `null` input.
Also, there are cases where inadvertent destructive changes can occur, as in the issue submitted below.
https://github.com/FasterXML/jackson-dataformat-xml/issues/607
Personally, I think that Nullability annotations should be given to public interfaces to avoid such problems.
`Jackson` is a huge project and we cannot fix everything at once, but I think we can proceed gradually.
There are several possible annotations to use, but to minimize the impact, it is better to choose one whose `RetentionPolicy` is not `RUNTIME`.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.