API endpoint for setting user email address (STAM-5) #177
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
Getting requirements to build wheel did not run succesfully due to and error in importing from setuptools.
Add a REST API endpoint for setting the user's email address if it's empty. Refs STAM-5
Refs STAM-5
jopesy
force-pushed
the
stam-5-user-email-form
branch
from
d3addb8 to
01df826
Compare
jopesy
changed the title
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.
Add a REST API endpoint for setting the user's email address if it's empty.
This is the case when an authentication provider such as PIKI library card or Suomi.fi is used to log in and the user doesn't have an email address available there. Allowing the user to set their email address in Respa ensures that the email address is saved to the User's detailsand having to include the
reserver_emailfield in reservation forms is not required.This also fixed the issue with the email address not being included in the access control request to Securitas Flow if it's missing from the user's details.
Refs STAM-5