Skip to content

feat(settings): Convert Pairing flow to React#20126

Draft
vbudhram wants to merge 1 commit intomainfrom
react-pair-conversion
Draft

feat(settings): Convert Pairing flow to React#20126
vbudhram wants to merge 1 commit intomainfrom
react-pair-conversion

Conversation

@vbudhram
Copy link
Contributor

@vbudhram vbudhram commented Mar 2, 2026

Because

This pull request

Issue that this pull request solves

Closes: (issue number)

Checklist

Put an x in the boxes that apply

  • My commit is GPG signed.
  • If applicable, I have modified or added tests which pass locally.
  • I have added necessary documentation (if appropriate).
  • I have verified that my changes render correctly in RTL (if appropriate).

Screenshots (Optional)

Please attach the screenshots of the changes made in case of change in user interface.

Other information (Optional)

This builds on #20119, so the diff is a bit larger. I tried to keep the diff small but the tests kinda made it bigger.

@vbudhram vbudhram force-pushed the react-pair-conversion branch 6 times, most recently from edf5ef9 to 2d4ad8a Compare March 3, 2026 14:50
@vbudhram vbudhram self-assigned this Mar 3, 2026
@vbudhram vbudhram force-pushed the react-pair-conversion branch from 2d4ad8a to e7b5293 Compare March 3, 2026 16:31
Implement the React versions of /pair and /connect_another_device with
full parity to the Backbone content-server originals. Add pre-render
redirect logic, device detection, Sync auth support checks, Glean
metrics wiring, and mode-detecting E2E tests. Clean up duplicate and
broken storybook stories across pairing pages.
@vbudhram vbudhram force-pushed the react-pair-conversion branch from e7b5293 to 014d6ba Compare March 3, 2026 19:56
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