Filename should not be included in the translations dictionary about nestjs-i18n HOT 3 CLOSED

@jorgecoca the options featurePrefix wouldn't work cause than you get duplicate paths.

i18n/
  en_US/
    intl_en_US.json
  es_ES/
    intl_es_ES.json

To access the translations you just use:
this.i18n.translate(intl_en_US.KEY, {lang: 'en_US'}) and
this.i18n.translate(intl_es_ES.KEY, {lang: 'es_ES'})

from nestjs-i18n.

• I agree that it could be better documented :)
• the prefix is used to save transactions in categories. (So in the design choice I made I tought it would be a good idea to save the translation per domain and have a file for each domain of transactions)
• I don't get this one sorry, cause you can still access both translations by using the path right?

I'm open to any solutions to make this a better library. So if you could clarify this we could probably make some changes in the documentation or design to solve this.

from nestjs-i18n.

Once I posted the message, I understood that adding the prefix in there was to allow us to have "feature/domain" translations, but the fact that it is hidden in the "string ID" that you want to provide, and not by an API, seems weird to me.

Maybe as part of the options object in the translate method? e.g. (see featurePrefix)

public translate(
    key: string,
    options?: {
      lang?: string;
      args?: Array<{ [k: string]: any } | string> | { [k: string]: any };
      featurePrefix?: string;
    },
  )

PS. Regarding your third bullet point, how would you access those strings if you have this folder structure, where the JSON files have the same string IDs?

i18n/
  en_US/
    intl_en_US.json
  es_ES/
    intl_es_ES.json

from nestjs-i18n.