Skip to content

fix: make SAGET/SASET responses reference target account#2360

Open
saschabuehrle wants to merge 1 commit intoergochat:masterfrom
saschabuehrle:fix/issue-1197
Open

fix: make SAGET/SASET responses reference target account#2360
saschabuehrle wants to merge 1 commit intoergochat:masterfrom
saschabuehrle:fix/issue-1197

Conversation

@saschabuehrle
Copy link
Copy Markdown

Bug

#1197 — SAGET and SASET responses use "your" wording even when an operator is reading or modifying another account.

Fix

  • Thread the target account context into displaySetting
  • For SAGET always-on, report "Stored always-on setting for account is ..."
  • For successful SASET, report "Successfully changed account settings for "
  • Keep existing wording unchanged for normal SGET/SSET

Testing

  • go test ./irc -run '^$' (package compile check)

Happy to address any feedback.

Greetings, saschabuehrle

Copy link
Copy Markdown
Member

@slingamn slingamn left a comment

Choose a reason for hiding this comment

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

Thank you very much for looking into this issue!

service.Notice(rb, fmt.Sprintf(client.t("Your stored always-on setting is: %s"), userPersistentStatusToString(stored)))
}
if actual {
service.Notice(rb, client.t("Given current server settings, your client is always-on"))
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Note that the issue applies here as well:

  1. anything in displaySetting that references "you" or "your"
  2. "Successfully changed your account settings" in nsSetHandler
  3. Possibly other places

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants