[MOB-98] Rename, delete, & more

[ameer2468]

This PR does the following:

• Several visual adjustments, making some elements smaller as they were too big.
• Browse screen location and tag sections redesigned
• Error handling for some actions (will do a few more in another PR)
• Rename and delete support
• Toast messages redesign

Notes:

There's currently issues with the Watcher which I believe Arnab is working on, some updates are not being reflected correctly.

[linear[bot]]

MOB-98 Rename & Delete support

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

| Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **spacedrive-landing** | ⬜️ Ignored ([Inspect](https://vercel.com/spacedrive/spacedrive-landing/CjLDXV6j7nRPaXGDue9Y17Af8haN)) | [Visit Preview](https://spacedrive-landing-git-mob-98-rename-delete-support-spacedrive.vercel.app) | | May 27, 2024 0:25am | | **spacedrive-web** | ⬜️ Ignored ([Inspect](https://vercel.com/spacedrive/spacedrive-web/9CG9369LreE6bPWVtBHZkHhNBYNr)) | [Visit Preview](https://spacedrive-web-git-mob-98-rename-delete-support-spacedrive.vercel.app) | | May 27, 2024 0:25am |

[utkubakir]

is CI job relevant here?

[ameer2468]

is CI job relevant here?

I just fixed the test after running it locally. Also finally fixed the annoying warning message that you would see on initial render in onboarding and in the app.

[utkubakir]

is CI job relevant here?

I just fixed the test after running it locally. Also finally fixed the annoying warning message that you would see on initial render in onboarding and in the app.

How? What was it lol

I am not a fan of these multiple useEffects to be honest, those functions are supposed to only run once on the app start but that might not be the case here

[ameer2468]

is CI job relevant here?

I just fixed the test after running it locally. Also finally fixed the annoying warning message that you would see on initial render in onboarding and in the app.

How? What was it lol

I am not a fan of these multiple useEffects to be honest, those functions are supposed to only run once on the app start but that might not be the case here

That's what the warning was about. You cannot run that code during the initialization of the App. The reason is it should only be run when buildInfo data is present. It's to prevent it from running during the rendering phase, and therefore they should be in a useEffect.

In that case, there's no harm in using effects, as that's what it should have been in the start.

https://stackoverflow.com/questions/62336340/cannot-update-a-component-while-rendering-a-different-component-warning