Skip to content

Conversation

sf-cboscenco
Copy link
Contributor

Description

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

  • (change1)

How to Test-Drive This PR

  • (step1)

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-cboscenco and others added 3 commits August 25, 2025 09:02
… version) (#2892) (#3173)

* Initial restore of base path PR

* Rename path functions

* Update commerce-sdk-react callbacks and slas private proxy endpoint

* Big update

* Replace getAppOrigin calls with useAppOrigin

* WIP - Filter the base path from all incoming requests to the server

* Remove base path from proxied requests + cleanup

* Use functions for proxy pathRewrite

* A bit of PR cleanup

* Lint cleanup

* More cleanup

* Fix tests

* Fix issues found by CI

* Lint for override asset

* Turn off slas private proxy

* Cleanup comments

* Update changelog entries

* Fix config

* Limit base path removal to /mobify or express route

* Adjust express filter

* Lint

* Fix dependency in generated apps

* Comment cleanup

* use envBasePath as a feature toggle for enabling the base path middleware

* Enable basepath removal middlware to handle express routes defined as regexes

* Apply suggestions

* Adjust app config template

* Use pathToRegexp rather than having manual regex interpretation

* escape the base path to not allow regex

* refactor

* Remove ?* from callback url

* Handle ? characters in express route

* Cache express regexes

* Handle properly formatted ()? express groups

* Comment cleanup

* Apply suggestions to reduce use of regex

* Add base path to social login redirectUri

* Lint

* Update comments and test

* Update test with more realistic scenario

* Remove path-to-regexp

* Refine convertExpressRouteToRegex further

* Move express route to regex logic to separate file

* Adjust logger and lock file

* Revert package-lock changes

---------

Signed-off-by: vcua-mobify <47404250+vcua-mobify@users.noreply.github.com>
Co-authored-by: vcua-mobify <47404250+vcua-mobify@users.noreply.github.com>
@sf-cboscenco sf-cboscenco requested a review from a team as a code owner August 25, 2025 19:25
@cc-prodsec
Copy link
Collaborator

cc-prodsec commented Aug 25, 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)

Copy link
Contributor

@sf-shikhar-prasoon sf-shikhar-prasoon left a comment

Choose a reason for hiding this comment

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

Approving this for now. We still need to go file by file and make sure all the files we have changed are needed. I feel like un-needed changes could have slipped in when porting v4 (Chakra V4) to v3 as these 2 have different folder structures.

We'll look at this diff and the diff in #3171, and fix anything we find in the subsequent PRs (PRs against this feature branch). But for now as things are working, I feel it's best to take these changes in and work from here.

@sf-cboscenco sf-cboscenco merged commit 0a9c248 into feature/manual-bonus-products-v3 Aug 25, 2025
23 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants