add i18n parser

Author: Jakub Łobos

i18next-parser.config.js

@@ -0,0 +1,58 @@
+export default {
+    contextSeparator: ":",
+    // Key separator used in your translation keys
+    createOldCatalogs: false,
+    // Save the \_old files
+    defaultNamespace: "translation",
+    // Default namespace used in your i18next config
+    defaultValue: "__NOT_TRANSLATED__",
+    // Default value to give to empty keys
+    indentation: 4,
+    // Indentation of the catalog files
+    keepRemoved: false,
+    // Keep keys from the catalog that are no longer in code
+    keySeparator: ".",
+    // Key separator used in your translation keys
+    // If you want to use plain english keys, separators such as `.` and `:` will conflict. You might want to set `keySeparator: false` and `namespaceSeparator: false`. That way, `t('Status: Loading...')` will not think that there are a namespace and three separator dots for instance.
+    // see below for more details
+    lexers: {
+        ts: ["JavascriptLexer"],
+        tsx: ["JsxLexer"],
+        default: ["JavascriptLexer"],
+    },
+    lineEnding: "auto",
+    // Control the line ending. See options at https://github.com/ryanve/eol
+    locales: ["en", "pl", "de"],
+    // An array of the locales in your applications
+    namespaceSeparator: ":",
+    // Namespace separator used in your translation keys
+    // If you want to use plain english keys, separators such as `.` and `:` will conflict. You might want to set `keySeparator: false` and `namespaceSeparator: false`. That way, `t('Status: Loading...')` will not think that there are a namespace and three separator dots for instance.
+    output: "public/static/locales/$LOCALE.json",
+    // Supports $LOCALE and $NAMESPACE injection
+    // Supports JSON (.json) and YAML (.yml) file formats
+    // Where to write the locale files relative to process.cwd()
+    input: undefined,
+    // An array of globs that describe where to look for source files
+    // relative to the location of the configuration file
+    sort: true,
+    // Whether or not to sort the catalog
+    skipDefaultValues: false,
+    // Whether to ignore default values.
+    useKeysAsDefaultValue: false,
+    // Whether to use the keys as the default value; ex. "Hello": "Hello", "World": "World"
+    // This option takes precedence over the `defaultValue` and `skipDefaultValues` options
+    verbose: false,
+    // Display info about the parsing including some stats
+    failOnWarnings: false,
+    // Exit with an exit code of 1 on warnings
+    customValueTemplate: null,
+    // If you wish to customize the value output the value as an object, you can set your own format.
+    // ${defaultValue} is the default value you set in your translation function.
+    // Any other custom property will be automatically extracted.
+    //
+    // Example:
+    // {
+    //   message: "${defaultValue}",
+    //   description: "${maxLength}", // t('my-key', {maxLength: 150})
+    // }
+};