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

Custom Ordering rules #84

Open
6 tasks done
Benehiko opened this issue Jan 26, 2023 · 1 comment
Open
6 tasks done

Custom Ordering rules #84

Benehiko opened this issue Jan 26, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Benehiko
Copy link
Contributor

Preflight checklist

Describe your problem

Currently the UserAuthCard only provides a hard-coded order of fields. e.g. the OIDC flows are always at the top and password flow fields below.

We should provide a way to have custom ordering on this.

For more information see this discussions https://github.com/orgs/ory/discussions/44

Describe your ideal solution

Have an object determining the ordering or a function to export the ordering to the client importing the library.

Workarounds or alternatives

None

Version

v0.0.1-alpha.28

Additional Context

No response

@Benehiko Benehiko added the enhancement New feature or request label Jan 26, 2023
@Benehiko Benehiko self-assigned this Jan 26, 2023
Copy link

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 label Jan 27, 2024
@zepatrik zepatrik removed the stale label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants