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

Translation / Add support for custom translations in @ory/elements-markup #166

Open
3 of 5 tasks
veteran29 opened this issue Oct 26, 2023 · 3 comments · May be fixed by #288
Open
3 of 5 tasks

Translation / Add support for custom translations in @ory/elements-markup #166

veteran29 opened this issue Oct 26, 2023 · 3 comments · May be fixed by #288

Comments

@veteran29
Copy link
Contributor

Preflight checklist

Ory Network Project

No response

Describe your problem

We're deploying self-hosted Ory Kratos, to speed up the project we've used the node self-serve UI from Ory.
During the implementation we've found out that unlike to its React counterpart you can't pass customTranslations to @ory/elements-markup components.

Describe your ideal solution

Addition of customTranslations parameter to elements-markup component-wrapper intl provider.

Workarounds or alternatives

I don't see other viable alternative.

Version

0.1.0-beta.11

Additional Context

No response

@Benehiko
Copy link
Contributor

Yes, you're right. We've only added the custom language support recently.

PRs are welcome!

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 Nov 10, 2024
@dmeijboom dmeijboom linked a pull request Nov 19, 2024 that will close this issue
6 tasks
@dmeijboom
Copy link

Would be great if the stale label can be removed. We're comitted to adding support for custom translations in @ory/elements-markup.

@github-actions github-actions bot removed the stale label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants