-
Notifications
You must be signed in to change notification settings - Fork 187
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(core): add customer account orders functionality #1639
Conversation
🦋 Changeset detectedLatest commit: 2ec0e3e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
4 Skipped Deployments
|
e709701
to
c61ffa8
Compare
@bc-alexsaiannyi I think we can squash this into one commit with a single changeset |
c61ffa8
to
f6f7da9
Compare
f6f7da9
to
d5221c4
Compare
d5221c4
to
0d4c801
Compare
0d4c801
to
60ec886
Compare
f953ffa
to
31655a9
Compare
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 there's a bit of refactoring needed here to optimize for performance. I left 🍹's where I think that is the case. I'm not blocking this PR from going through though, but we should probably tackle these optimizations during release freeze.
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.
For order details, we should rely on slugs to fetch details. Lets create a page for /account/orders/[id]
to display order content, instead of using search params to know what to render.
We also should rely more on Suspense boundaries and loading states to make sure this page is speedy.
core/app/[locale]/(default)/account/(tabs)/orders/_components/orders-content.tsx
Outdated
Show resolved
Hide resolved
31655a9
to
2410b6c
Compare
cb21e0f
to
d813b53
Compare
d813b53
to
520cbd1
Compare
520cbd1
to
4987ef7
Compare
6aa9489
to
1ff4bd2
Compare
1ff4bd2
to
addf5ce
Compare
Hey @jorgemoya, I think that mentioned concerns have been addressed in separate PRs that are already merged in this branch. Can you please look at it once more if we're good to go🙏 |
feat(core): add order details components & update page data feat(core): add translations for order details page, small fixes for multi consignments order refactor(core): update header and account home page links after refactoring fix(core): simplify UI with respect to available data fix(core): move orders connection under customer in respect with api fix(core): update quantity of items in order truncated card refactor(core): update getTranslations for orders fix(core): separate promotions and coupons for order summary refactor(core): update OrderItemFragment according to API changes refactor(core): update in respect with storefront token changes feat(core): add images for order items refactor(core): Next15 upgrade asynchronous searchparams for orders page feat(core): add path to PDP for Orders fix(core): update styles for product snippet refactor(core): add filters to orders query refactor(core): update order page to use slug refactor(core): add suspense boundaries & skeleton for product snippet in orders test(core): add account orders test
12b3723
to
2ec0e3e
Compare
⚡️🏠 Lighthouse reportLighthouse ran against https://catalyst-latest-pn9rpraxb-bigcommerce-platform.vercel.app 🖥️ DesktopWe ran Lighthouse against the changes on a desktop and produced this report. Here's the summary:
📱 MobileWe ran Lighthouse against the changes on a mobile and produced this report. Here's the summary:
|
What/Why?
This PR combines and brings Order functionality to Customer's Account.
Testing
locally
Account_Orders.mov