-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: Create scheduling process skeleton #25
Conversation
frontend/src/components/pages/Scheduling/DonationInformation.tsx
Outdated
Show resolved
Hide resolved
frontend/src/components/pages/Scheduling/DonationInformation.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Hanlin Cheng <h62cheng@uwaterloo.ca>
Co-authored-by: Hanlin Cheng <h62cheng@uwaterloo.ca>
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.
I think this is a good skeleton template to work off for implementing the scheduling workflow! 😄
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.
Nice work!! For future frontend tickets, please include a screenshot or a video in the PR as well. It would be easier for the people reviewing!
navigation, | ||
}: SchedulingStepProps) => { | ||
const { previous, next } = navigation; | ||
const history = useHistory(); |
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.
Do we need this here?
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.
hmm yeah don't think we need this, we can remove it when working on this page
Notion ticket link
Initial Scheduling Structure - https://www.notion.so/uwblueprintexecs/Initial-Scheduling-Structure-83f15a6202fe476a99524954a8b24fac
Implementation description
Note 1-5 are using the useStep functionality in
/schedule
route while 6. Thank You page is its own route/schedule/confirmation
01e5509e-c298-4080-96d3-fb6face6bbb2.mp4
Steps to test
What should reviewers focus on?
Checklist