futurice / futurice/freesound-android
API POJO field nullability
Open
issue::feature
pr::in progress
- Dominant language
- Java
- Stars
- 86
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently some fields are defined as nullable, simply because the API, being outside of the control of the application, could not define values for certain fields by error, even though they are required. We should not be propagating nullability so far into the application, ideally the network layer should enforce the desired nullability.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.