fix(api,food): nullable fields weren't nullable anymore. #789
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 Problem
Nullable fields weren't nullable anymore when parsing JSON queries in the Food API. See card.
🍰 Solution
This patch uses a more flexible utilitity from
Decode.Extra
to relax nullable value check. It also ensures always responding with errors encoded as JSON, for consistency.🏝️ How to test
Unit tests have been added so we're probably safe here, but toying around with the API manually might be a good idea.
Production
Patch version
A
null
transform is now accepted:Decoding errors are now wrapped in JSON: