-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/comment deleting with activities installed #45848
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it makes sense to introduce a global storage in the app just to store ids or deleted comments in 2-3 components.
If storing deleted
state in the comment it self is a problem, it's enough to store it in the parent.
Besides, it seems that the initial issue is that adding a comment triggers an entire tab reload through loading state. What's when Comment
instances are being destroyed and re-mounted without old deleted
state.
@ShGKme Would you have any suggestions on how to not make the tab reload then? I'm having trouble figuring out the activities API, thank you :) |
So, I made a deeper look at the app. With activity app case it is indeed not possible to store data in the parent, because on the Activity tab there is no parent between comments and the form. Every comment is a new Vue app. So, as a simple workaround from the server side, it is a good workaround. A better solution would be to adjust Activity API to not reload everything on change. But with the current approach, it is not so simple. So, let's fix Ferdinand's suggestion and go with it for now cc @GretaD |
💯 agree |
794c0bd
to
68ba038
Compare
/backport to stable28 |
/backport to stable29 |
/compile amend / |
68ba038
to
f60b4f5
Compare
/compile amend / |
f60b4f5
to
243d763
Compare
The branch is outdated. Other PRs touched the frontend bundles. It will need a rebase and a recompile. |
243d763
to
52ab6a0
Compare
/compile amend / |
52ab6a0
to
79aac6e
Compare
79aac6e
to
01cce6e
Compare
|
/compile amend / |
094b38e
to
c4422cd
Compare
conflicts -> needs rebase + rebuild |
a52fcf2
to
6123505
Compare
/compile amend / |
Signed-off-by: Grigory Vodyanov <scratchx@gmx.com> Signed-off-by: Grigory V <scratchx@gmx.com> Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
6123505
to
bd7c29c
Compare
Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
The backport to # Switch to the target branch and update it
git checkout stable29
git pull origin stable29
# Create the new backport branch
git checkout -b backport/45848/stable29
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bd7c29c3
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45848/stable29 Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
The backport to # Switch to the target branch and update it
git checkout stable28
git pull origin stable28
# Create the new backport branch
git checkout -b backport/45848/stable28
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick bd7c29c3
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45848/stable28 Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
When doing the backports @GVodyanov please directly include #46643 |
Summary
Fixes issue where you:
TODO
Checklist