-
Notifications
You must be signed in to change notification settings - Fork 24
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
Offset in key preview on homepage. #128
Comments
@cadesalaberry could you share the project or an example project with me? |
Sorry, it took me some time to generate the files, and strip the unnecessary content. I uploaded the pertinent files on https://github.com/cadesalaberry/l10ns-offset if you care to have a look. Cheers |
@tinganho did you have time to checkout the issue ? As I understood it, the if you add a language to the localization ( You will then have two files with the keys in different orders. Do you think that is where it comes from ? |
@cadesalaberry I looked into the example project. Seems like the project doesn't have the key |
You could probably manually try to correct those files. By adding one entry into the other and see what happens. |
@cadesalaberry the timestamps and orders in the shared project is very misaligned. The mentioned entry is just one case, but I can find many more. Do you happen to know how they became misaligned? |
That's because I added I think ordering the |
I think I will just use the order of the default language. And remove the timestamp entries on non-default languages. Though I think this change is quite big and more suitable for a future release. |
Alright, sounds good ! Are you talking about the v3 ? |
Yes, though I'm afraid it won't be happening soon. |
On the first page, everything is fine, but when I load the second page, the previews start to get mixed up.
In my example here,
SIGNUP__LOCALIZATION_EMPTY
is correct.However when I load more content, the key
AWARDS__CARD__SCORE__UNIT
displaysInstead of
I started investigating, but haven't found out from where it was coming yet.
I suspect it might be related to key ordering in the json files but can't confirm as of now.
@tinganho Could you give me a hand on this issue ?
The text was updated successfully, but these errors were encountered: