-
Notifications
You must be signed in to change notification settings - Fork 14
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
Request IR by text message #248
Conversation
tests/integration/individual_response/test_individual_response.py
Outdated
Show resolved
Hide resolved
tests/integration/individual_response/test_individual_response.py
Outdated
Show resolved
Hide resolved
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.
Couple of minor comments
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.
Happy with the changes, feature is as expected.
As discussed, just waiting on decision about lowering the max age for URLSafeTimedSerializer
should be/whether there should be one and if not it should be URLSafeSerializer
.
Co-authored-by: James Gardiner <[email protected]>
The app doesn't work in Docker with the latest datastore library as the way emulator credentials work has been changed in 1.15. We are fixing on 1.14 temporarily, as soon as this merges we will update to 1.15 in a separate pull request.
What is the context of this PR?
Adds the journey to request an individual response by text message shown in the prototype. Encrypts the mobile number from view in the url. Validation is not handled and will follow on a separate card.
NB: I couldn't see why the person_id would be present in the url so I've not included it. This also follows how the post url structure. I'm away until the end of the month so this will need to be picked up by someone else in my absence.
How to review
See if you agree with the approach.