Skip to content

W 18998603 Route 'Order Status' 'footer link to a new Order Status Page#2795

Merged
sf-deepali-bharmal merged 2 commits intofeature/order-management-pluginfrom
W-18998603/RouteToANewOrderStatusPage
Jul 15, 2025
Merged

W 18998603 Route 'Order Status' 'footer link to a new Order Status Page#2795
sf-deepali-bharmal merged 2 commits intofeature/order-management-pluginfrom
W-18998603/RouteToANewOrderStatusPage

Conversation

@sf-deepali-bharmal
Copy link
Contributor

Description

This is an initial PR to add routing from a footer Order Status link to a new page.
I will create more PRs to add details in this new page.

UX : https://www.figma.com/proto/FE1DzN6LPFOoP598gymW8U/-258--PWA-Kit-Order-Management-Plugin?page-id=5001%3A55009&node-id=7001-324713&p=f&t=GaZc2PTx5ppuAJGa-0&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=7001%3A299133

Types of Changes

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Documentation update
  • Breaking change (could cause existing functionality to not work as expected)
  • Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

  • Removing a public function or component or prop
  • Adding a required argument to a function
  • Changing the data type of a function parameter or return value
  • Adding a new peer dependency to package.json

Changes

  • Add a new Order Status page.
  • Route Order Status nav link from footer to this page

How to Test-Drive This PR

  • Click on the Order Status link from footer

Checklists

General

  • Changes are covered by test cases
  • CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

  • There are no changes to UI

or...

Localization

  • Changes include a UI text update in the Retail React App (which requires translation)

@sf-deepali-bharmal sf-deepali-bharmal requested a review from a team July 11, 2025 22:53
@sf-deepali-bharmal sf-deepali-bharmal requested a review from a team as a code owner July 11, 2025 22:53
@sf-deepali-bharmal sf-deepali-bharmal added the skip changelog Skip the "Changelog Check" GitHub Actions step even if the Changelog.md files are not updated label Jul 11, 2025
@cc-prodsec
Copy link
Collaborator

cc-prodsec commented Jul 11, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@sf-deepali-bharmal sf-deepali-bharmal changed the title W 18998603 Route footer link to a new Order Status Page W 18998603 Route 'Order Status' 'footer link to a new Order Status Page Jul 11, 2025
@sf-deepali-bharmal sf-deepali-bharmal added the ready for review PR is ready to be reviewed label Jul 11, 2025

test('renders mobile version by default', () => {
renderWithProviders(<Footer />)
// This link is hidden initially, but would be shown for desktop
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure I understand this. Is this saying some footer links aren't shown on initial store load?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Footer shows different links in mobile vs desktop screens.
And mobile is the default/initial option for the app hence it says - mobile view might have few footer links hidden but has more links in desktop view.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok, "rendered mobile version by default" was confusing - not sure how that hidden-then-shown part is tested here.

Copy link
Contributor

@sf-emmyzhang sf-emmyzhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick on one of the existing tests for mobile view, but other than that LGTM

import OrderStatusPage from '@salesforce/retail-react-app/app/pages/order-status/index.jsx'

describe('OrderStatusPage', () => {
it('renders the order status page', () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

preferably don't us "it" and i've been told before not to use getByTestId if possible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad. I will take care of this in the next PR.

@sf-deepali-bharmal sf-deepali-bharmal merged commit ccc0c81 into feature/order-management-plugin Jul 15, 2025
36 checks passed
sf-deepali-bharmal added a commit that referenced this pull request Jul 15, 2025
…ge (#2795)

* Initial empty commit for order-management-plugin

* Order Status footer link routes to a new Order Status Page
sf-deepali-bharmal added a commit that referenced this pull request Jul 21, 2025
…ge (#2795)

* Initial empty commit for order-management-plugin

* Order Status footer link routes to a new Order Status Page
sf-deepali-bharmal added a commit that referenced this pull request Aug 19, 2025
…ge (#2795)

* Initial empty commit for order-management-plugin

* Order Status footer link routes to a new Order Status Page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for review PR is ready to be reviewed skip changelog Skip the "Changelog Check" GitHub Actions step even if the Changelog.md files are not updated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants