Purchase History and Purchase Details pages #49
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
… tracking number to job in main.types, added styled avatar component
…n to Geometry in main.types
…ional in frontend
… purchase details page
…ledAvatar component
aaronkim218
changed the title
|
Lets discuss before merging |
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.
Description
Includes Purchase History and Purchase Details pages (only for designers). Nav dropdown contains Purchase History link that leads to Purchase History page (link only displays if current user is a designer). Purchase History page lists all of a designer's jobs, with most recent jobs displaying first. Clicking a job leads to Purchase Details page which shows details like shipping address, tracking number, price... Purchase Details page styled exactly like figma
Added StyledAvatar component, and changed any existing Avatars to StyledAvatar.
Added tracking number and estimated delivery date to job schema in frontend and backend
Changed location field of an address to match how it is stored in backend
How Has This Been Tested?
Tested locally
Checklist