633 allow survey answers to be multiselect #639
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lfilmeyer
force-pushed
the
633-allow-survey-answers-to-be-multiselect
branch
from
81d6422 to
c9ff1b7
Compare
lfilmeyer
force-pushed
the
633-allow-survey-answers-to-be-multiselect
branch
from
c9ff1b7 to
43bf6a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
answers, a string array, tosurvey_answers. Accepts this field onPOST /survey_visits& displays it onGET /survey_visitsand GET/survey_visit/:idOpen question: Do we care that the data in
survey_answers.answeris not migrated tosurvey_answers.answers? I assume not, but heads up that existing data hasanswers: []