Settings flow UI nodes filtering
@jonas-jonas ci sta già lavorando.
Dal 15/10/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
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.
- Lingua principale
- TypeScript
- Stelle
- 188
- Fork
- 80
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ory/elements
-
Needs Triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Needs Triage
Difficoltà 5/5 Più di una settimana Idoneità per principianti 22/100
-
enhancement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
-
good first issue help wanted upstream
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
-
good first issue help wanted upstream
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
Tutte le issue di ory/elements
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 76/100
logto-io/logto#9837 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 76/100
lingdojo/kana-dojo#32964 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
Documentation status: needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
mastra-ai/mastra#28194 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
priority-low refactor-3
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 3 giorni