We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
choose between null, nan or not having the attribute or other options
Acceptance criteria: Check that specification is clear about the management of empty fields or attributes, see:
The text was updated successfully, but these errors were encountered:
Added sentence in specification: Missing values: If a property is optional or has an empty or null value, consider dropping the property from the JSON, unless there's a strong semantic reason for its existence (taken from https://softwareengineering.stackexchange.com/questions/285010/null-vs-missing-key-in-rest-api-response )
See https://docs.google.com/document/d/16d0MVh48bFLvWsa5-B_Hy-cby1rGWdnNojWOJpUcOvA/edit?usp=sharing
Demo implementation updated to comply with that.
Sorry, something went wrong.
tloubrieu-jpl
No branches or pull requests
choose between null, nan or not having the attribute or other options
Acceptance criteria:
Check that specification is clear about the management of empty fields or attributes, see:
The text was updated successfully, but these errors were encountered: