Skip to content

Conversation

@backportbot
Copy link

@backportbot backportbot bot commented Oct 18, 2024

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.

@backportbot backportbot bot added this to the Nextcloud 29.0.9 milestone Oct 18, 2024
@susnux susnux force-pushed the backport/48425/stable29 branch from ab0f13d to 0d1c5e3 Compare October 28, 2024 14:01
@susnux susnux marked this pull request as ready for review October 28, 2024 14:01
@susnux susnux force-pushed the backport/48425/stable29 branch from 0d1c5e3 to 0eb5717 Compare October 28, 2024 14:01
@susnux
Copy link
Contributor

susnux commented Oct 28, 2024

/compile

@susnux susnux force-pushed the backport/48425/stable29 branch from 208f497 to a82e41f Compare October 29, 2024 12:20
@susnux susnux enabled auto-merge October 29, 2024 12:20
@Altahrim Altahrim mentioned this pull request Oct 30, 2024
4 tasks
@susnux susnux force-pushed the backport/48425/stable29 branch 2 times, most recently from b8ca901 to caf0d4b Compare October 30, 2024 12:38
@nextcloud-command nextcloud-command force-pushed the backport/48425/stable29 branch 2 times, most recently from a39d401 to 483f0d6 Compare October 30, 2024 14:38
@susnux susnux force-pushed the backport/48425/stable29 branch 2 times, most recently from 0bd8fcf to 58fb9eb Compare October 30, 2024 18:16
@Altahrim
Copy link
Collaborator

/compile amend /

This was referenced Nov 5, 2024
@Altahrim Altahrim removed this from the Nextcloud 29.0.9 milestone Nov 7, 2024
@Altahrim Altahrim added this to the Nextcloud 29.0.10 milestone Nov 7, 2024
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 <[email protected]>
@susnux susnux force-pushed the backport/48425/stable29 branch from 4e6d314 to 8588e49 Compare November 7, 2024 15:40
TODO: Drop when we support Node 22.

Signed-off-by: Ferdinand Thiessen <[email protected]>
Signed-off-by: Ferdinand Thiessen <[email protected]>
@susnux susnux force-pushed the backport/48425/stable29 branch from 8588e49 to ca83966 Compare November 7, 2024 16:37
@susnux susnux merged commit 6b2ea4f into stable29 Nov 7, 2024
113 checks passed
@susnux susnux deleted the backport/48425/stable29 branch November 7, 2024 16:51
@skjnldsv skjnldsv mentioned this pull request Nov 27, 2024
4 tasks
Sign up for free to 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