Allow empty valid json objects in write api #31

Merged
merged 2 commits into from Apr 3, 2013

Conversation

Projects
None yet
2 participants
@robyoung
Contributor

robyoung commented Apr 3, 2013

Previously empty arrays or empty objects would cause a 400 because
they're falsy.

robyoung and others added some commits Apr 3, 2013

Allow empty valid json objects in write api
Previously empty arrays or empty objects would cause a 400 because
they're falsy.
@gtrogers

This comment has been minimized.

Show comment Hide comment
@gtrogers

gtrogers Apr 3, 2013

Contributor

Renamed the test because we aren't checking that an empty list gets stored, only that our validation doesn't bounce it.

Contributor

gtrogers commented Apr 3, 2013

Renamed the test because we aren't checking that an empty list gets stored, only that our validation doesn't bounce it.

gtrogers added a commit that referenced this pull request Apr 3, 2013

Merge pull request #31 from alphagov/empty-json
Allow empty valid json objects in write api

@gtrogers gtrogers merged commit 7958843 into master Apr 3, 2013

1 check was pending

default Build #128 is running on Jenkins
Details

gtrogers added a commit that referenced this pull request Aug 23, 2013

Merge pull request #31 from alphagov/empty-json
Allow empty valid json objects in write api
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment