Skip to content

Conversation

@MarsCandyBars
Copy link
Contributor

@MarsCandyBars MarsCandyBars commented Nov 22, 2025

๐ŸŽŸ๏ธ Tracking

AC-1159

๐Ÿ“” Objective

Whether enabling or disabling SSO, event logs would read "SSO turned on". Adjusted the disabledSso object to be "SSO turned off"

๐Ÿ“ธ Screenshots

New behavior:

image

โฐ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

๐Ÿฆฎ Reviewer guidelines

  • ๐Ÿ‘ (:+1:) or similar for great changes
  • ๐Ÿ“ (:memo:) or โ„น๏ธ (:information_source:) for notes or general info
  • โ“ (:question:) for questions
  • ๐Ÿค” (:thinking:) or ๐Ÿ’ญ (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • ๐ŸŽจ (:art:) for suggestions / improvements
  • โŒ (:x:) or โš ๏ธ (:warning:) for more significant problems or concerns needing attention
  • ๐ŸŒฑ (:seedling:) or โ™ป๏ธ (:recycle:) for future improvements or indications of technical debt
  • โ› (:pick:) for minor or nitpick changes

@claude
Copy link

claude bot commented Nov 22, 2025

Claude finished @MarsCandyBars's task โ€”โ€” View job


Code Review Complete

  • Read changed files and PR diff
  • Check for related files that may need updates
  • Evaluate PR description quality
  • Provide comprehensive review feedback

Summary

The fix correctly addresses the duplicate "SSO turned on" message bug by changing disabledSso to show "SSO turned off". The change is minimal, correct, and localized translations already have the proper values.

Findings

Finding 1: PR title uses inconsistent style with past tense "fixed" instead of present tense

Finding 2: Other locale files already have correct translations but may be inconsistent with en


Finding 1: PR title uses inconsistent style with past tense "fixed" instead of present tense (๐Ÿ’ญ)

apps/web/src/locales/en/messages.json:7126

The PR title uses past tense "AC-1159 fixed disabledSso duplicate event log" which is inconsistent with the commit message style typically used in this repository. Based on recent commits, titles should use present tense imperative mood.

Suggested rewrite:

[AC-1159] Fix disabledSso duplicate event log message

This is a minor stylistic point and doesn't affect functionality.

Finding 2: Other locale files already have correct translations but may be inconsistent with en (๐Ÿ’ญ)

apps/web/src/locales/*/messages.json

I checked several major locale files (en_GB, fr, es, de) and found they already contain the correct "SSO turned off" translations:

  • en_GB: "SSO turned off"
  • fr: "SSO dรฉsactivรฉ"
  • es: "SSO desactivado"
  • de: "SSO deaktiviert"

This suggests the bug was limited to the en locale. However, this raises a question: how did the other locales get the correct translation while en had the wrong one? Was this a previous localization sync that missed updating the source en locale?

This doesn't require any action in this PR, but it might be worth understanding how the translations diverged to prevent similar issues in the future.


Technical Correctness

The change is technically correct:

  • The code in event.service.ts:375 references this.i18nService.t("disabledSso")
  • The fix changes the English message from "SSO turned on" โ†’ "SSO turned off"
  • The screenshot confirms the new behavior correctly displays "SSO turned off" for disable events
  • Other locale files already have correct translations

PR Description Quality

The PR description is well-structured and complete:

  • โœ… Clear objective explaining what and why
  • โœ… Screenshot showing the new behavior
  • โœ… Jira ticket linked
  • โœ… Reminders checklist included

The only minor suggestion is the title style mentioned in Finding 1.

@github-actions
Copy link
Contributor

Logo
Checkmarx One โ€“ Scan Summary & Details โ€“ 6110d2ee-abc3-423f-9aa6-2eac2f710caf

Great job! No new security vulnerabilities introduced in this pull request

@MarsCandyBars MarsCandyBars requested review from a team and BTreston November 22, 2025 02:16
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