forked from Heroic-Games-Launcher/HeroicGamesLauncher
-
Notifications
You must be signed in to change notification settings - Fork 0
/
i18next-parser.config.js
112 lines (94 loc) · 3.06 KB
/
i18next-parser.config.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
module.exports = {
contextSeparator: '_',
// Key separator used in your translation keys
createOldCatalogs: false,
// Save the \_old files
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})
// }
defaultNamespace: 'translation',
// Default namespace used in your i18next config
defaultValue: '',
// Default value to give to empty keys
failOnWarnings: false,
// Exit with an exit code of 1 on warnings
indentation: 4,
// Indentation of the catalog files
input: ['src/**/*.{ts,tsx}', 'electron/**/*.{ts,tsx}'],
// An array of globs that describe where to look for source files
// relative to the location of the configuration file
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: [
{
attr: 'i18nKey', // Attribute for the keys
lexer: 'JsxLexer'
}
]
},
lineEnding: 'auto',
// Control the line ending. See options at https://github.com/ryanve/eol
locales: [
'bg',
'ca',
'cs',
'de',
'el',
'en',
'es',
'et',
'fa',
'fi',
'fr',
'gl',
'hr',
'hu',
'ja',
'ko',
'id',
'it',
'ml',
'nl',
'pl',
'pt',
'pt_BR',
'ru',
'sv',
'ta',
'tr',
'uk',
'vi',
'zh_Hans',
'zh_Hant'
],
// 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/locales/$LOCALE/$NAMESPACE.json',
// Supports $LOCALE and $NAMESPACE injection
// Supports JSON (.json) and YAML (.yml) file formats
// Where to write the locale files relative to process.cwd()
skipDefaultValues: false,
// Whether to ignore default values.
sort: true,
// Whether or not to sort the catalog
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: true
// Display info about the parsing including some stat
}