webuipoc: UI implementation to reactWeb

[Moeez905]

Eslint configured in our Zap React App.

Issue Reference:
#8287.

[thc202]

This needs to integrate the latest changes.

[Moeez905]

Ready for review: did code cleanup, conflicts resolve and rebase.

[Moeez905]

Ready for review: did code cleanup, conflicts resolve and rebase.

Conflict resolved - Ready for review

[Moeez905]

This PR is ready to review

[kingthorin]

It has conflicts. Though that doesn't prevent review, but it'll need to be addressed before merge.

[Moeez905]

It has conflicts. Though that doesn't prevent review, but it'll need to be addressed before merge.

Resolved them just now

[thc202]

The build is failing.

[njmulsqb]

The build is failing.

I am unable to understand the reason it's failing. npm i is working fine locally. Do you see any specific issue?

[kingthorin]

Click checks, pick one of the failed jobs, look at the log.

[njmulsqb]

Its stating that npm ci run failed, but why is it even executing at first place? It's not defined in package.json file.

[kingthorin]

Probably a bad merge commit. You'd be better off rebasing and addressing conflicts.

[thc202]

The ci is to do a clean install: https://docs.npmjs.com/cli/v10/commands/npm-ci worth running that locally to make sure all is correct.

[njmulsqb]

Re-doing npm i solved the build failing problem.

[psiinon]

I get the same error when trying to build this as per the CI build: 'npm ci' can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
We cant review this PR unless it builds ☹️

[psiinon]

Still failing to build :/

[Moeez905]

Still failing to build :/

Fixed.

[kingthorin]

Seems to have a ton of unrelated commits again.

[Moeez905]

Seems to have a ton of unrelated commits again.

I'm struggling with rebase, can you tell me exact way or cmds to get this done

[kingthorin]

To provide commands to fix it I'll have to clone it later and try.

As for rebasing, the normal process is:

git fetch upstream
git rebase upstream/main
git push --force

[Moeez905]

It will take forever to resolve conflicts and rebase; what's the best practice here, should I rebase after every few commits?

[psiinon]

If I know no one else has changed the code I'm working on then I just do a mixed reset, not sure if thats good practice or not..

[kingthorin]

I can't seem to figure out what you've done 😞

[Moeez905]

There are so many conflicts :( I am trying to resolve in rebase for past 30 mins or so, any other solution I can try to fix this?

[thc202]

Don't worry about the commits.

[psiinon]

The build is failing due to changes in other add-ons ☹️

[Moeez905]

The build is failing due to changes in other add-ons ☹️

any idea how to get this done , I've tried npm i and npm ci

[kingthorin]

Nice work. Glad you got this passing again!

[thc202]

IMO the tree should look like more the Sites tree (or the example web UI, i.e. show path segments rather than the full URI). I guess it can be improved later.

[thc202]

Thank you!