-
-
Notifications
You must be signed in to change notification settings - Fork 5
Form responses storing and validation #17
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
Conversation
Wrong button, meant to request changes! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments made above!
This PR looks good and seems like a good base for form responses. Once this is through I'll get to work looking at how to render these forms on the frontend in a good way and how to collect responses.
Thanks!
There are a couple of other places where status codes should be returned. We'll also standardise the error format at some point. Don't worry about those, implement the changes in this PR and I'll open a PR in the next day or so to change things — but they are not critical. |
Co-authored-by: Joe Banks <[email protected]>
Closes #8
Created models for form responses, added captcha and blacklist validation and updated user validation. Now also stores data to DB.
Also added duplicate ID validation for forms as side change (found bug when testing).