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

API addition for translations #259

Merged
merged 1 commit into from Mar 8, 2021

Conversation

PrimordialMoros
Copy link
Contributor

Adds a method to check if a translation key has any registered translations.

This allows one to easily handle a missing translation key using a custom fallback.

@zml2008
Copy link
Member

zml2008 commented Jan 13, 2021

It's not possible to know serverside whether or not a translation exists - the translatable component supports any key defined in a client resource pack as well.

@PrimordialMoros
Copy link
Contributor Author

I was thinking about plugin registered keys that are unlikely to exist on client resource packs. Perhaps, should mention this limitation in the documentation, or change the method name to better reflect that?

@zml2008 zml2008 added this to the 4.7.0 milestone Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants