-
-
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
Revert scope of direct editing to avoid changing session user #35360
Conversation
0b6bc19
to
fd82bb0
Compare
fd82bb0
to
fabec08
Compare
fabec08
to
8dd1bfb
Compare
8dd1bfb
to
fef7fd0
Compare
fef7fd0
to
687a8dd
Compare
687a8dd
to
37b2911
Compare
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.
Walked through this today with @juliushaertl during one on one.
Seems legit ;)
37b2911
to
b2ee2a9
Compare
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.
Seems good.
I'm curious to know what were the possible side effects of not removing the user ID from the session.
…e session Signed-off-by: Julius Härtl <jus@bitgrid.net>
b2ee2a9
to
47bc024
Compare
This is useful to avoid unexpected behaviour which already was fixed in nextcloud/text#3476 (comment) but could happen for other direct editing implementations in the future as well.
Checklist