Skip to content

components 0.7.2: Form.EmailPassword shows a line under the email; the profile and email-change snackbars fixed - #211

Merged
joelmsanto merged 1 commit into
mainfrom
auth/email-change-messages-2026-11-13
Nov 15, 2026
Merged

joelmsanto merged 1 commit into
mainfrom
auth/email-change-messages-2026-11-13

Conversation

@joelmsanto

Copy link
Copy Markdown
Contributor

What

  • Form.EmailPassword takes emailHelperText (optional, already localized by the host): Paper's HelperText under the email, in its section, as FormBusinessInfo places its own. Without the prop the form renders as before.
  • snackbar.emailUpdated and snackbar.profileUpdated were crossed in es.json, and profileUpdated was Spanish in en.json. Both now carry the owner's approved words (2026-11-13); emailUpdated takes %{email}.
  • A story and a test for the line. Version 0.7.2, not published yet.

Why

The email-change review (owner, 2026-11-13). Saving a new email showed the profile's text in Spanish under English, or the other one's text. And CustomerApp's profile must say why an email that came with a social sign-in is locked («Este correo viene de tu cuenta de Google y no se cambia aquí.»).

Checked

Form/__tests__/FormEmailPassword.test.js 2/2, Localization/__tests__/parity.test.js 6/6.

Order

Merge, then publish 0.7.2 from a clean export of main (owner's order). CustomerApp then pins it by npm install --save-exact in its own PR, which passes emailHelperText and the address to snackbar.emailUpdated.

🤖 Generated with Claude Code

…der the email; the profile and email-change snackbars say what happened

- Form.EmailPassword takes `emailHelperText` (optional, localized by the
  host): Paper's HelperText under the email, in its section, as
  FormBusinessInfo places its own. CustomerApp's profile says there why an
  email that came with a social sign-in cannot be changed (owner 2026-11-13).
  Without the prop the form is what it was.
- `snackbar.emailUpdated` and `snackbar.profileUpdated` were crossed in
  es.json, and `profileUpdated` was Spanish in en.json. Now in the owner's
  words (2026-11-13): «Te enviamos un enlace a %{email}. Tu correo cambia
  cuando lo abras.» / "We sent a link to %{email}. Your email changes when you
  open it."; «Perfil actualizado.» / "Profile updated." `emailUpdated` takes
  the address.
- A story and a test for the line.

Tests: Form/__tests__/FormEmailPassword.test.js 2/2,
Localization/__tests__/parity.test.js 6/6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@joelmsanto

Copy link
Copy Markdown
Contributor Author

The red suites (ratchet) check is the install step, not this change: npm ci (then npm install) cannot resolve @jmstechnologiesinc/react-native-google-places-autocomplete@2.4.13, which wants react@>=19, against the root's react@18.3.1. main fails the same way since 2026-11-11 (push run after #210, and every PR since). This PR touches only packages/components (the form, its translations, the version). Not fixed here: it changes the dependency tree, and React versions are not changed without the owner.

🤖 Generated with Claude Code

@joelmsanto
joelmsanto merged commit 791f8b1 into main Nov 15, 2026
1 check failed
@joelmsanto

Copy link
Copy Markdown
Contributor Author

Correction to my comment of 2026-11-14. I wrote that main fails the same way «since 2026-11-11». That is wrong.

The owner left moving this CI out of the work (2026-11-14). Until then, I run the install and the suites by hand on every RNC PR.

🤖 Generated with Claude Code

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