[FIX] Incorrect folder size after a move operation

[CodeObsessed-1234]

Description

This PR fixes an issue where the folder size was not updating correctly after replacing a file with the same name. Previously, the folder size showed duplicate files until a manual refresh was performed.

Fix Details

• Auto-refreshes folder size after file replacement.
• Uses fileOperationsViewModel.performOperation(FileOperation.RefreshFolderOperation(...)).
• Ensures correct quota updates in spacesListViewModel.refreshSpacesFromServer().

Related Issues

Fixes #<4505>

How to Test

1. Move a file to a folder that already contains the same file.
2. Click Replace in the warning dialog.
3. The folder size should update automatically without manual refresh.

Checklist

• Added a changelog entry in changelog/unreleased/
• Tested the fix manually
• Followed code contribution guidelines

preview.mp4

[CLAassistant]

All committers have signed the CLA.

[jesmrec]

Thanks for your contribution!! team will review it and come back to you with feedback about the code quality and functional review. Stay tuned to the code review and QA-phase!

[joragua]

Good job @CodeObsessed-1234!🏅One thing about commits: we don't usually link the issue to the commit message because in the pull request we have that reference. Also, I left some comments for you to review them:

[CodeObsessed-1234]

I've addressed all the requested changes. Please review again when you get a chance. Thanks!

[joragua]

More changes here @CodeObsessed-1234!

[joragua]

Nice job @CodeObsessed-1234! It's ready for QA! Let's move it 🚀

[jesmrec]

My QA feedback:

The solution works, since the displayed folder size is the correct one. The fix, changing the folder size is a bit blinky, but i don't consider that as blocker since the problem is edge-case.

The most-desired solution would be not to update the list till the user's final decision is made, avoiding the refresh and the blink in the size. But, at least, the current fixes the glitch.

Let's go for it and feel free to think in a better approach ;)

Approved.

[CodeObsessed-1234]

@jesmrec Thanks for the feedback! I understand the concern about the blinky effect. This fix resolves the glitch for now, but I’ll keep the suggested improvement in mind for future refinements. 😊..

[CodeObsessed-1234]

Hi,
It looks like the Bitrise check is still pending. Should I do anything from my side, or can it be merged as is? Let me know if any action is needed. Thanks!

[jesmrec]

Hi,
It looks like the Bitrise check is still pending. Should I do anything from my side, or can it be merged as is? Let me know if any action is needed. Thanks!

no action required from your side, BiRise is pending for an internal fix, as soon as it is fixed your contribution will be in. Thanks!!

[JuancaG05]

Hi @CodeObsessed-1234! Would you be able to rebase this branch against the master branch? I'm not sure if there is new content in master which is not here, but in case there isn't, could you find a way to trigger again the checks of the PR (for example, adding a new commit and removing it afterwards with an interactive rebase if necessary)? We made a tweak in some repo settings, so let's see if we can make it pass now 😀

[CodeObsessed-1234]

Hi @JuancaG05
I’ve successfully rebased this branch against the master branch. There were no new changes in master that weren’t already included here.

To re-trigger the PR checks, I added an empty commit and pushed it.
Could you or someone from the team approve it so the tests can proceed? Thanks!"

[joragua]

Hi @CodeObsessed-1234! Can you remove the two empty commits that you pushed with an interactive rebase? The problem with bitrise is still happening so, we will fix it as soon as possible. If you don't know how to do it, let us know and we will help you 😄

[JuancaG05]

@CodeObsessed-1234 hey, let's wait until we tell you the final settings are configured and then you can remove those empty commits, to finally merge it 😬 sorry for the inconveniences and thanks for the patience!

[joragua]

Here we go! CI/CD it's ready! @CodeObsessed-1234, now you can rebase this branch against master branch and remove the empty commits. Thanks a lot! 😄