Skip to content

fix: prioritize group settings over user settings - #37

Merged
daopunk merged 1 commit into
mainfrom
fix/translate-me-over-group-bug
Aug 14, 2026
Merged

fix: prioritize group settings over user settings#37
daopunk merged 1 commit into
mainfrom
fix/translate-me-over-group-bug

Conversation

@daopunk

@daopunk daopunk commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

!translate-all-on en es confirmed English ↔ Spanish, but that author's messages could still auto-translate to Persian if they had a leftover personal pair (!translate-me-on fa en). Reply !translate es looked fine because it never reads stored pairs.

While group-wide is on, everyone now uses the group pair. !translate-me-on is refused until !translate-all-off; leftover personal pairs stay saved and apply again after group-wide is off. Detection also skips a third language instead of forcing it into the pair (so Spanish in a Persian/English pair is not labeled English → Persian).

Test plan

  • !translate-all-on en es, then send English and Spanish — they swap even after a prior !translate-me-on fa en
  • !translate-me-on while group-wide is on — refused, with a note to !translate-all-off first
  • !translate-all-off then !translate-me-on — personal auto works again
  • Reply !translate es still translates the quoted message
  • Local: npm run ci (fmt, clippy, coverage ≥90%)

@daopunk
daopunk merged commit ac675cf into main Aug 14, 2026
2 checks passed
@daopunk
daopunk deleted the fix/translate-me-over-group-bug branch August 15, 2026 19:20
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.

1 participant