Closed ZaLiTHkA closed 1 month ago
Hey! Would you be open to also share the en.json
?
Hey! Would you be open to also share the
en.json
?
would just a portion of it suffice? or do you need the full file?
I think, the file is not necessary as it was exported from tolgee. I'll need to check it on windows.
@JanCizmar just FYI, @stepan662 was helping answer a few of my questions earlier in this discussion thread, which is when I discovered this particular issue.
..and the path separator strikes again.
thanks @stepan662, just tested the oh-so-freshly released 2.1.6
and it is indeed fixed.
I'm about a week into my adventures with Tolgee, and just this morning I discovered an interesting discrepancy between how the CLI tool behaves on Windows vs Linux.
for context, this is what I'm currently working with:
1000
string limit is in place720
strings in total, from360
translation keys with2
languagesnvm
on Linux using Bashnvs
on Windows using PowerShell 7my app project exists within a Nx monorepo workspace, so do take note of the following paths, relative to the workspace root:
./apps/my-app/
./apps/my-app/src/assets/i18n/
./apps/my-app/.tolgeerc.json
the crux of the issue here is that
tolgee push
works perfectly from my Zorin OS (Debian based) environment, but fails with aInvalid request data [status: 400, code: plan_translation_limit_exceeded]
error from my Windows 11 Pro environment.the translation files that I'm trying to push are the very same files that I downloaded from my hosted Tolgee project, so this should simply update existing keys in place, no new keys are being added.
with the following command:
tolgee -v -c ./apps/my-app/.tolgeerc.json push
I get the following output from Windows (personal details redacted):
my
.tolgeerc.json
file is as follows (project ID redacted as with CLI output):please do let me know if you need any further details regarding this..