Closed ployniti closed 1 month ago
I'd like to address some of concerns with this, particularly with how data is stored and displayed, before we think about commiting to this route and merging it
ClientDataTable.js
now displays each client data/submission per row.
The table creates column and rows dynamically from the data from client_data_list
.
Describe your changes
Modify
models.py
to haveQuestions
andClientData
tables. The schema/ER diagram for the relationship between the two tables can be found here: https://github.com/users/smithev95/projects/1?pane=issue&itemId=65436393Add code to dynamically generate questions based on the rows in
Questions
table.Add functionality to submit answers to questions and store them as rows in
ClientData
table.Align functionalities with https://github.com/smithev95/NEFP-Capstone/pull/36
Add functionality to add new question by adding a row in the
Questions
table.Add functionality to update existing question by updating the row in the
Questions
table.Add functionality to delete question. The logic and flow are very similar to that of updating existing question so I just added another submit button in the
question_editor.html
form. The decision to whether delete or update is made insubmit_update
. Might be worthwhile renaming some of the functions so that they reflect the dual purpose here (ex.update_question
->update_delete_question
).Issue ticket number and link
https://github.com/smithev95/NEFP-Capstone/issues/35 https://github.com/smithev95/NEFP-Capstone/issues/29 https://github.com/smithev95/NEFP-Capstone/issues/28 https://github.com/smithev95/NEFP-Capstone/issues/23
Testing done
Local UI and database testing.
Checklist before requesting a review