feat: User accessibility information input #353
Conversation
HappyNTH
added
enhancement
HappyNTH
force-pushed
the
feat/accessibility-info-integration
branch
from
767c7cc to
282fd79
Compare
HappyNTH
force-pushed
the
feat/accessibility-info-integration
branch
from
282fd79 to
cb146ac
Compare
| @click=" | ||
| () => { | ||
| booking.accessibilityInfo = newAccessibility; | ||
| updateAPI(); |
There was a problem hiding this comment.
Just double-checking it is the case on the back-end too; will the prod team be emailed about an update made to accessibility info after the booking has been already confirmed?
There was a problem hiding this comment.
And if accessibility info is removed (e.g. the person in the wheelchair is no longer coming, and their seat is taken by somebody else in the family instead), will that also be emailed to prod?
There was a problem hiding this comment.
This is a great catch, and led me to a further investigative chain. I've pulled the PR back to draft, since it's going to need some further API work to go with it to make sure that emails are sent properly.
|
All looks pretty good - just a small number of minor tweaks (or not, just questions), and then good to go |
HappyNTH
force-pushed
the
feat/accessibility-info-integration
branch
from
4642757 to
2740efa
Compare
Implementing
accessibilityInfo, allowing users to input any access(ability) requirements and admins/box office to view it (resolves #320)