Skip to content
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] System messages triggering when values don't change. #20845

Closed

Conversation

AlexanderKanakis
Copy link

@AlexanderKanakis AlexanderKanakis commented Feb 21, 2021

Proposed changes (including videos or screenshots)

Issue(s)

#19038

Steps to test or reproduce

Further comments

@@ -129,12 +129,14 @@ const settingSavers = {
saveRoomName(rid, value, user);
},
roomTopic({ value, room, rid, user }) {
if (value !== room.topic) {
// room inits with room.topic as undefined. If value is empty string while room.topic is still undefined, do not set topic.
if (value !== room.topic && (value || room.topic)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may fail if you explicitly set the room topic as '' (like, when you remove the topic at all)
The same will happens for the rest of the comparisons

Maybe a direct check for null or undefined would be better here?

@CLAassistant
Copy link

CLAassistant commented Dec 17, 2021

CLA assistant check
All committers have signed the CLA.

@ggazzo ggazzo added this to the 5.4.0 milestone Nov 2, 2022
@gabriellsh gabriellsh changed the title [FIX] Issue #19038 fix [FIX] System messages triggering when values don't change. Nov 3, 2022
@gabriellsh
Copy link
Member

Closing since requested changes weren't addressed. This will be implemented in a separate PR and will be linked here shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants