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

I18n configuration doesn't seem to work for block tunes #2688

Closed
GuillaumeOnepilot opened this issue Apr 17, 2024 · 1 comment
Closed

I18n configuration doesn't seem to work for block tunes #2688

GuillaumeOnepilot opened this issue Apr 17, 2024 · 1 comment
Labels

Comments

@GuillaumeOnepilot
Copy link
Contributor

Describe a bug.
I'm trying to add some translations for my tunes, but it seems that the translations are not registered

Steps to reproduce:

  1. Create a custom tune
  2. Add some translations with the correct tunes name
  3. No translations are registered

Expected behavior:
I use i18Next, so it should display the translations key with dots, and not the default key

Screenshots:
Screenshot 2024-04-17 at 09 21 59
Screenshot 2024-04-17 at 09 22 06

Device, Browser, OS:
Chrome, macOS

Editor.js version:
Any version I tried

@GuillaumeOnepilot
Copy link
Contributor Author

I'm an Idiot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant