Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation and examples missing for form fields ordering #1236

Closed
christian-roggia opened this issue Apr 16, 2021 · 4 comments
Closed

Documentation and examples missing for form fields ordering #1236

christian-roggia opened this issue Apr 16, 2021 · 4 comments
Labels
stale Feedback from one or more authors is required to proceed.
Milestone

Comments

@christian-roggia
Copy link

According to #176 it is possible to define the ordering of form fields but documentation about it seems to be completely missing and so are examples.

I would also like to know whether it is possible to also define the ordering of OIDC fields (e.g. have OIDC buttons before the username / password textboxes).

@zepatrik
Copy link
Member

zepatrik commented Apr 16, 2021

You can always reorder stuff in your UI. Better don't rely on Kratos to ensure a certain order, but rather use some mapping to render your UI according to your UX decisions. See also #1196
#205 is only a gimmick and not a real feature with guarantees.

@aeneasr
Copy link
Member

aeneasr commented Apr 22, 2021

We've improved the ordering in the Ory Kratos 0.6 branch but it is not possible to really customize it. As @zepatrik said this will be probably the burden of the UI implementation :)

@aeneasr
Copy link
Member

aeneasr commented Apr 22, 2021

But yeah we need docs for that!

@aeneasr aeneasr added this to the v0.10.0-alpha.1 milestone Mar 7, 2022
@aeneasr aeneasr modified the milestones: v0.10.0-alpha.1, v1.0.0 May 30, 2022
@github-actions
Copy link

github-actions bot commented Jul 5, 2023

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Jul 5, 2023
@github-actions github-actions bot closed this as completed Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

3 participants