Settings flow UI nodes filtering

未关闭
  • 哪里不对？
#576 3 条评论 2 个 reaction 已指派 1 人 在 GitHub 查看

@jonas-jonas 已经在做这个了。

开始于 2025年10月15日。

评估

这个 Issue 还没有评估数据。

描述

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
主要语言
TypeScript
星标
188
派生
81
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ory/elements 的其他 Issue

查看 ory/elements 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。