Skip to content

refactor: UI code cleanup and folder restructure#814

Open
Shubhangi-Microsoft wants to merge 1 commit intodevfrom
psl-ui-refractoring
Open

refactor: UI code cleanup and folder restructure#814
Shubhangi-Microsoft wants to merge 1 commit intodevfrom
psl-ui-refractoring

Conversation

@Shubhangi-Microsoft
Copy link
Copy Markdown
Contributor

This pull request reorganizes the frontend and frontend-server directories under a new unified src/App structure, updating all related build, deployment, and configuration scripts to match the new paths. Additionally, it introduces Redux Toolkit and related libraries to the frontend dependencies, laying groundwork for advanced state management.

Directory and Path Refactoring

  • Moved src/app/frontend and src/app/frontend-server into src/App and src/App/server, updating all references in build scripts, deployment scripts, Dockerfiles, workflow files, and infrastructure configs to use the new paths. This includes renaming files, changing directory names, and adjusting build contexts and copy commands. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]

Frontend Dependency Updates

  • Added Redux Toolkit (@reduxjs/toolkit), React Redux (react-redux), and related libraries (redux, redux-thunk, reselect, immer) to the frontend dependencies in package.json and package-lock.json to enable scalable state management in the React app. [1] [2] [3] [4] [5] [6] [7] [8]

Dockerfile and Build Improvements

  • Updated the Dockerfile and .dockerignore to match the new directory structure, simplifying the build context and copy commands for both the frontend and server. [1] [2] [3] [4]

Documentation Updates

  • Updated all documentation and technical guides to reference the new src/App paths for building, running, and troubleshooting the frontend and server. [1] [2] [3]

Build and Deployment Script Adjustments

  • Modified PowerShell and shell scripts for packaging, deploying, and running the frontend locally to use the new directory structure, ensuring all build and copy commands work as expected. [1] [2] [3] [4] [5] [6]## Purpose
  • ...

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

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.

1 participant