Skip to content

[Domain Control] [Release 4] Add Restrict default login selection to DomainGroupDetailsPage - #308

Closed
jakubstec wants to merge 555 commits into
war-in/domains/security-group-details-pagefrom
jakubstec/domains/security-group-details-page-group-permissions2
Closed

[Domain Control] [Release 4] Add Restrict default login selection to DomainGroupDetailsPage#308
jakubstec wants to merge 555 commits into
war-in/domains/security-group-details-pagefrom
jakubstec/domains/security-group-details-page-group-permissions2

Conversation

@jakubstec

@jakubstec jakubstec commented Mar 16, 2026

Copy link
Copy Markdown
Member

Explanation of Change

Add `` setting according to the issue linked below.

Fixed Issues

$ #80133
PROPOSAL:

Tests

  1. Open Workspaces
  2. Open Domains and select a domain where you are an admin
  3. Open Groups
  4. ...
  • Verify that no errors appear in the JS console

Offline tests

...

QA Steps

Same as Tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@war-in
war-in force-pushed the war-in/domains/security-group-details-page branch from cc668cd to cc281b1 Compare March 16, 2026 14:40
@jakubstec
jakubstec force-pushed the jakubstec/domains/security-group-details-page-group-permissions2 branch from 5b01086 to efd2e6e Compare March 16, 2026 14:55
@jakubstec
jakubstec marked this pull request as draft March 18, 2026 08:28
shubham1206agra and others added 27 commits April 21, 2026 09:48
Swap withCurrentUserPersonalDetails HOC for the useCurrentUserPersonalDetails hook.
No behavior change — both read the same Context — but removes the HOC wrapper and
aligns the component with the current codebase convention.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the unused preferredLocale prop and read it from useLocalize() inside the
component. The prop was never threaded through PureReportActionItem, so the
component was silently falling back to CONST.LOCALES.DEFAULT — this change fixes
that latent bug and removes one prop from the interface.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tions

Replace the emojiReactions prop with a direct useOnyx subscription on
REPORT_ACTIONS_REACTIONS. Use the shared getEmptyObject<ReportActionReactions>()
helper for the stable empty default (matches BaseQuickEmojiReactions /
MiniQuickEmojiReactions).

Clean up the full prop chain:
- PureReportActionItem no longer takes/forwards emojiReactions; its memo loses
  the deepEqual(emojiReactions) entry.
- The isOnSearch ? {} override is replaced with an !isOnSearch mount gate in the
  parent, so on search we skip the mount (and the subscription) entirely.
- ReportActionItem, ReportActionsListItemRenderer, DuplicateTransactionItem and
  ReportActionItemParentAction drop the prop and the now-unused useOnyx calls /
  selectors that only existed to source it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yuwenmemon and others added 29 commits April 23, 2026 10:56
…height-in-landscape-mode

[Landscape] Fix popup content is not fully shown
refactor getReasonAndReportActionThatHasRedBrickRoad to use isOffline from useNetwork
…-spend-87974

[No QA] Update navigation terminology from "Reports" to "Spend"
Update both New Expensify and Expensify Classic "Avoiding common scams"
help articles to include a new section for users who receive a magic
code they didn't request. The new guidance reassures users that an
unrequested code alone doesn't mean their account is compromised,
reminds them not to share the code, and reserves the "lock your
account" recommendation for cases where the code was actually shared
or the user's email is believed to be compromised.

Co-authored-by: David Barrett <quinthar@users.noreply.github.com>
[CP Stag] Put spend rule summary and editing behind env guard
…bug-tax-field-missing

fix: bulk edit, tax field missing for unreported expenses
…estedMagicCodeGuidance

[No QA] Update help docs with proportionate guidance for unrequested magic codes
…tic-concierge-typing-updates

Remove optimistic Concierge typing updates for delayed follow-up responses
…yGoogleapis

Bump @sentry/webpack-plugin and googleapis with lockfile update
@jakubstec jakubstec closed this Apr 24, 2026
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.