Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Settings flow UI nodes filtering

Aperta
#576 3 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@jonas-jonas ci sta già lavorando.

Dal 15/10/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Needs Triage
Preflight checklist
Ory Network Project

No response

Describe your problem

We’re building a custom email-only update component using the component from @ory/elements-react.
To do this, we filter the settings flow’s UI nodes so that only the email-related nodes are displayed. This allows users to update their email address without seeing any of the other settings fields (password, profile info, etc.).

This setup works correctly on the initial settings flow. However, when submitting the form with an invalid email, we receive a 400 response and new UI nodes — but this new set of nodes includes all settings flow nodes, not just the filtered ones.
Since the request is made internally by the component, we currently don’t have a way to apply our filtering logic after the response updates the flow.

Describe your ideal solution

Our goal is to have a settings flow that only includes the email update UI nodes, even after validation errors or flow updates triggered by the form submission.
Essentially, we want to:

  • Keep the filtered state consistent across flow updates, or find a way to request only specific UI nodes from the initial settings.
  • Maintain full Ory validation and error handling behavior.
Workarounds or alternatives

A workaround would be to have access to the onSubmit function from the Settings component so we can manually filter out UI nodes and keep just the ones we need.

Version

1.0.0

Additional Context

We would like to have a component as the one in the image attached in this request. The component would be a single email update component, not showing the other fields. And we would use the same approach for other settings updates, like password or username.

Image
Lingua principale
TypeScript
Stelle
188
Fork
80
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ory/elements

Tutte le issue di ory/elements

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.