Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DateAdapter should not be null-safe per default #77

Open
renner opened this issue Jun 10, 2015 · 0 comments
Open

DateAdapter should not be null-safe per default #77

renner opened this issue Jun 10, 2015 · 0 comments

Comments

@renner
Copy link
Member

renner commented Jun 10, 2015

The current generically used DateAdapter is null-safe per default: whenever an expected date is missing in the returned JSON the library would just silently accept that. Instead we should probably fail per default and rather support the declaration of optional fields allowing us to accept missing values for selected date fields that may or may not be returned by the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant