Is there any ways to get an Array from the json file directly?

[DongwonTTuna]

Hello! 😊

I appreciate you for creating this great library for qwik. It has been very helpful to me.

I am aware that there is a method to parse strings into arrays, but I would like to inquire if there is a way to retrieve an array from a JSON file.

the JSON file is.

{
  "common": {
    "slides": ["visual4.png","visual1.png","visual2.png","visual3.png"]
  }
}

In the next-i18next library, I have been able to achieve this using
Array.from(t("slides", { returnObjects: true }))

Also, I would like to know if there are any possible ways to save an array as a default value directly to JSON?

Currently, I am saving it in the following way:

{t("common.slides@@visual4.png,visual1.png,visual2.png,visual3.png")
.split(",")
.map((item, index) => {return (<div>{blablabla}</div>)})

Thank you for reading!

[robisim74]

Hi @DongwonTTuna ,

Currently, only arrays of keys are supported out of the box. But I think it would be possible to implement key => array as well according to the syntax you suggested:

from (jsx)

const myArray = t("common.slides@@visual1.png,visual2.png");

to (json)

{
  "common": {
    "slides": ["visual1.png","visual2.png"]
  }
}

rendered as

const myArray = ["visual1.png","visual2.png"];

inlined as

const myArray = $lang('it-IT') && ["visual1-it.png","visual2-it.png"] || ["visual1.png","visual2.png"];

If you like it, I'll try to do some testing and add key => array support in the next version of the library.

[DongwonTTuna]

ok, I found the bug is caused by updating libary to 0.7.0

I don't know why it is but when I downgrade to 0.6.0, It works.

[robisim74]

Thanks for your feedback! There was a bug with array of objects (downgrade to v.0.6.0 it's not an option, because objects were not supported yet).

I released the patch v.0.7.1 which should fix the bug.

Now you should be able to use:

const ArrayObjects = t<Translation[]>('app.ArrayObjects@@[{"one":"1","two":"2"},{"one":"1","two":"2"},{"one":"1","two":"2"}]')

[DongwonTTuna]

Thank you for quickly updating again!🤩

I tried to use it immediately, but it still causes errors.

The problems are as follows:

• The npm run build does not work. (same error as the previous version)
• The qwik-speak-extract command applies the value of a different file instead of the default value. (See the picture below for details)

The following picture shows the contents of the json file that I used as the default value and that is set as the Default Language.
I set Korean as the default language because English is not my native language.

  const imageArray = t<Translation[]>('product.hycera@@["v1677989410/bioden/hycera1_gjjzdt","v1677989411/bioden/hycera2_v46x7l","v1677989411/bioden/hycera3_lqhmo5"]');

i18n/ko/product.json

{
  "product":{
    "hycera": [
      "v1677989410/bioden/hycera1_eng_up5keo",
      "v1677989411/bioden/hycera2_eng_hu8rcp",
      "v1677989411/bioden/hycera3_eng_fmuw4c"
    ]
  }
}

However, as you can see, the string in ko/product.json was passed as the default value for the hycera array in en/product.json, not the value behind @@.

The value should have been as follows.

i18n/ko/product.json

{
  "product":{
    "hycera": [
      "v1677989410/bioden/hycera1_gjjzdt",
      "v1677989411/bioden/hycera2_v46x7l",
      "v1677989411/bioden/hycera3_lqhmo5"
    ]
  }
}

I am not sure of the exact reason why this error occurred, but there were also cases where the array value in cn/product.json became the default value.

In my opinion, during the build process, it is decoded and static pages are created for each language, but with the addition of this feature, there seems to be an error in that process.

Thank you for your time. I appreciate your help 😊

[robisim74]

About the extraction If I understood correctly, do you expect the default value to override the value in the json file? The default value is used in dev mode and during extraction for any language where the value doesn't exist in the json file. If it already exists, of course it is not overwritten, otherwise you would lose the translations already made. If you intend to regenerate it into the json file, you should delete it (just the value or the whole file) before running the qwik-speak-extract command.

About the build I did a repro: https://stackblitz.com/edit/qwik-speak-vcw7wz?file=src%2Froutes%2F[...lang]%2Findex.tsx where an array is used (already extracted in json files, because extract command doesn't work directly in StackBlitz). If you stop the server, and do npm run preview, you'll see that it works. Could you try to recreate the problem, and open a issue?

Thanks!

[DongwonTTuna]

Hello, thank you for your response.😊

To reproduce this error, I have created a simple qwik project at the following GitHub repository: https://github.com/DongwonTTuna/qwik-speak-ErrExample.git.

1. Firstly, please check the json files for each language.
2. Next, please run npm install && npm run dev to confirm that it works as expected.
3. Then, please try running npm run build to confirm that an error occurs.
4. Finally, please use npm run qwik-speak-extract to confirm that the contents of each json file are overwritten with values in a different language other than the default values. (this may need to run the command several times with original i18n files)

Thank you!