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

Empty workflow.tasks.task.answers array turns into null #743

Closed
brian-c opened this issue Apr 14, 2015 · 0 comments · Fixed by #803
Closed

Empty workflow.tasks.task.answers array turns into null #743

brian-c opened this issue Apr 14, 2015 · 0 comments · Fixed by #803
Assignees
Labels
Milestone

Comments

@brian-c
Copy link
Contributor

brian-c commented Apr 14, 2015

Putting an empty array as the answers to a "single"-type task seems to respond with that value set to null instead.

Ask me if you need to see a demo.

Discovered by @chrislintott

@edpaget edpaget added the bug label Apr 15, 2015
@edpaget edpaget added this to the v0.0.7 milestone Apr 15, 2015
@edpaget edpaget self-assigned this May 4, 2015
edpaget pushed a commit to edpaget/Panoptes that referenced this issue May 5, 2015
Closes zooniverse#743

Because most users of Rails are apparently unable or unwilling to check
params before passing arguments to AR#find, Rails converts empty arrays
in params to nil. This makes 0 sense to me, but whatever, it's easy to
turn off.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants