Skip to content

[stable30] fix(files): Ensure renaming state is correctly reset - #48731

Merged
susnux merged 2 commits into
stable30from
backport/48425/stable30
Oct 21, 2024
Merged

[stable30] fix(files): Ensure renaming state is correctly reset#48731
susnux merged 2 commits into
stable30from
backport/48425/stable30

Conversation

@backportbot

@backportbotbackportbotBot commented Oct 16, 2024

Copy link
Copy Markdown

Backport of #48425

Warning, This backport's changes differ from the original and might be incomplete ⚠️

Todo

  • Review and resolve any conflicts
  • Remove all the empty commits

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@susnux
susnux marked this pull request as ready for review October 17, 2024 16:12
Problem: Is a node is renamed and the new name is out of the current
visible list of nodes the component will be recycled, this means
the props will change, so when the `onRename` functions is about to reset
the state the `this.source` will point to a different node.
To fix this, but also to separate business logic from visual representation,
the logic is moved into the renaming store and the component is only
responsible for rendering.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux
susnuxforce-pushed the backport/48425/stable30 branch from 7328b3a to d4685cbCompareOctober 21, 2024 11:53
@susnux

Copy link
Copy Markdown
Contributor

/compile

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@susnux
susnux merged commit 876262d into stable30Oct 21, 2024
@susnux
susnux deleted the backport/48425/stable30 branch October 21, 2024 13:35
@AltahrimAltahrim mentioned this pull request Oct 30, 2024
2 tasks
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@susnux@artonge@blizzz@nextcloud-command