The page you are looking for does not exist.
8 |9 | 12 | 15 |
16 |{JSON.stringify(auth, null, 2)}
24 | 156 | {body} 157 |
158 | ); 159 | }); 160 | FormMessage.displayName = 'FormMessage'; 161 | 162 | export { 163 | useFormField, 164 | Form, 165 | FormItem, 166 | FormLabel, 167 | FormControl, 168 | FormDescription, 169 | FormMessage, 170 | FormField, 171 | }; 172 | -------------------------------------------------------------------------------- /i18next-parser.config.ts: -------------------------------------------------------------------------------- 1 | // i18next-parser.config.js 2 | 3 | export default { 4 | contextSeparator: '_', 5 | // Key separator used in your translation keys 6 | 7 | createOldCatalogs: true, 8 | // Save the \_old files 9 | 10 | defaultNamespace: 'translation', 11 | // Default namespace used in your i18next config 12 | 13 | defaultValue: '', 14 | // Default value to give to keys with no value 15 | // You may also specify a function accepting the locale, namespace, key, and value as arguments 16 | 17 | indentation: 2, 18 | // Indentation of the catalog files 19 | 20 | keepRemoved: true, 21 | // Keep keys from the catalog that are no longer in code 22 | // You may either specify a boolean to keep or discard all removed keys. 23 | // You may also specify an array of patterns: the keys from the catalog that are no long in the code but match one of the patterns will be kept. 24 | // The patterns are applied to the full key including the namespace, the parent keys and the separators. 25 | 26 | keySeparator: '.', 27 | // Key separator used in your translation keys 28 | // 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. 29 | 30 | // see below for more details 31 | lexers: { 32 | hbs: ['HandlebarsLexer'], 33 | handlebars: ['HandlebarsLexer'], 34 | 35 | htm: ['HTMLLexer'], 36 | html: ['HTMLLexer'], 37 | 38 | mjs: ['JavascriptLexer'], 39 | js: ['JavascriptLexer'], // if you're writing jsx inside .js files, change this to JsxLexer 40 | ts: ['JavascriptLexer'], 41 | jsx: ['JsxLexer'], 42 | tsx: ['JsxLexer'], 43 | 44 | default: ['JavascriptLexer'], 45 | }, 46 | 47 | lineEnding: 'auto', 48 | // Control the line ending. See options at https://github.com/ryanve/eol 49 | 50 | locales: ['en', 'fr'], 51 | // An array of the locales in your applications 52 | 53 | namespaceSeparator: ':', 54 | // Namespace separator used in your translation keys 55 | // 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. 56 | 57 | output: 'app/locales/$LOCALE/$NAMESPACE.json', 58 | // Supports $LOCALE and $NAMESPACE injection 59 | // Supports JSON (.json) and YAML (.yml) file formats 60 | // Where to write the locale files relative to process.cwd() 61 | 62 | pluralSeparator: '_', 63 | // Plural separator used in your translation keys 64 | // If you want to use plain english keys, separators such as `_` might conflict. You might want to set `pluralSeparator` to a different string that does not occur in your keys. 65 | // If you don't want to generate keys for plurals (for example, in case you are using ICU format), set `pluralSeparator: false`. 66 | 67 | input: 'app/**/*.{ts,tsx}', 68 | // An array of globs that describe where to look for source files 69 | // relative to the location of the configuration file 70 | 71 | sort: false, 72 | // Whether or not to sort the catalog. Can also be a [compareFunction](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#parameters) 73 | 74 | verbose: false, 75 | // Display info about the parsing including some stats 76 | 77 | failOnWarnings: false, 78 | // Exit with an exit code of 1 on warnings 79 | 80 | failOnUpdate: false, 81 | // Exit with an exit code of 1 when translations are updated (for CI purpose) 82 | 83 | customValueTemplate: null, 84 | // If you wish to customize the value output the value as an object, you can set your own format. 85 | // 86 | // - ${defaultValue} is the default value you set in your translation function. 87 | // - ${filePaths} will be expanded to an array that contains the absolute 88 | // file paths where the translations originated in, in case e.g., you need 89 | // to provide translators with context 90 | // 91 | // Any other custom property will be automatically extracted from the 2nd 92 | // argument of your `t()` function or tOptions in