I created and implemented the Fakemissing trips survey that takes the pre-existing places-notes code and adds the Missing Trip survey to that. The code as is mostly already handles it...
Testing:
The only part that is not handled, is answer.js, meaning that the survey can never "Save"/complete because there is no code to handle this.
My questions is: do we want to create a generic "Answer" to new surveys so that no matter what they can respond? Or will we need to create an answer in LABEL_FUNCTIONS (in answer.js) for each new survey we create, meaning that e-mission-phone will require an update for each new survey type we enter
One thing that I see is that if we are storing user input, additionally to creating a new unique answer for each new survey added, we will also need to add the user-input storage on e-mission-server. So no matter what, whenever we create a brand new survey we need to change both e-mission-phone and e-mission-server
I created and implemented the Fake missing trips survey that takes the pre-existing
places-notes
code and adds the Missing Trip survey to that. The code as is mostly already handles it...Testing:
The only part that is not handled, is
answer.js
, meaning that the survey can never "Save"/complete because there is no code to handle this. My questions is: do we want to create a generic "Answer" to new surveys so that no matter what they can respond? Or will we need to create an answer inLABEL_FUNCTIONS
(inanswer.js
) for each new survey we create, meaning that e-mission-phone will require an update for each new survey type we enter