You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## High Level Overview of Change
This PR runs `prettier` on all Explorer files (it seems that it wasn't
properly run on non-JS/TS files before). It also configures CI and CLI
scripts to check `prettier` as well, and sets up some basic pre-commit
settings.
This PR does not make any code changes, only linting changes.
### Context of Change
General repo cleanup
### Type of Change
- [x] Chore
### Codebase Modernization
N/A
## Before / After
<!--
If just refactoring / back-end changes, this can be just an in-English
description of the change at a technical level.
If a UI change, screenshots should be included.
-->
## Test Plan
Works locally. CI passes.
Copy file name to clipboardExpand all lines: docs/translating.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
1. Add the new language code and language name to the map `supportedLanguages` in [/src/i18n/baseConfig.ts](../src/i18n/baseConfig.ts)
6
6
2. Create a folder in [/public/locales/](../public/locales) with the language code as its name.
7
7
3. Add a new file, `translations.json`, to the new folder.
8
-
4. Translate all the entries. If you prefer to use the English version just set the value to `null`.
8
+
4. Translate all the entries. If you prefer to use the English version just set the value to `null`.
9
9
10
10
Example file: [/public/locales/ja-JP/translations.json](../public/locales/ja-JP/translations.json)
11
11
@@ -14,12 +14,13 @@
14
14
When making changes to the base (English) language file follow the guide based on the type and scope of the change.
15
15
16
16
### New Entry
17
+
17
18
1. Create entry in `en-US/translations.json`
18
19
2. Add an entry to all other `translation.json` files. Set the value to be `null` (which means it will default to using the English version).
19
20
20
21
## Existing Entry
22
+
21
23
1. Update the entry in `en-US/translations.json`
22
24
2. If the meaning does **NOT** change materially, you can leave them as is. Ex. "Please check your transaction hash" => "Please check your transaction hash or CTID."
23
25
3. If the entry has a new meaning than before, set the value to `null` in all other `translation.json` files.
24
-
25
-
*Note that changing a translation to `null` causes it to fall back to the English version, and is a signal to language contributors that they may want to provide a fresh localization.*
26
+
_Note that changing a translation to `null` causes it to fall back to the English version, and is a signal to language contributors that they may want to provide a fresh localization._
0 commit comments