sheet-i18n 1.4.0-canary.5 → 1.4.0-canary.6

package/README.md

@@ -268,20 +268,20 @@ The `I18nStore` manages type-safe translation states, ensuring consistency acros
 - **`supportedLocales`**: Array of supported locale strings.
 - **`defaultLocale`**: The default locale, included in `supportedLocales`.
 - **`localeSet`**: An object where keys match `supportedLocales`, and values are translation sets.
-- **`typeSafe(optional, default = true)`**: An optional boolean indicating whether to use type-safe translations.
+- **`typeSafe(optional, default = false)`**: An optional boolean indicating whether to use type-safe translations.
 
 > 💡 **typeSafe?** <br/>
-> I18nStore is type-safe by default. So, basically, you can't add the translation data that is not defined in the locale Json files. However, for fast development, you can off the typeSafe option manually.
+> I18nStore doesn't enforce adherence to your locale JSON definitions by default. This means that you can add translation data even if it isn’t pre-defined in your locale JSON files. However, if you prefer to enforce strict type-safety, you can manually enable the typeSafe option which allows you to notice the auto-completed list in translation data.
 >
 > ```tsx
-> // typeSafe: false
+> // typeSafe: true
 > const YourComponent = () => {
->   // useTranslation(sheetTitle: string)
+>   // "useTranslation" shows the autocompletion suggestions
 >   const { t } = useTranslation('header');
 >
 >   return (
 >     <div>
->       {/* t(key: string): any */}
+>       {/* "t" function shows the autocompletion suggestions */}
 >       <button>{t('login')}</button>
 >     </div>
 >   );
@@ -637,17 +637,17 @@ export const i18nStore = new I18nStore({
 ```
 
 > 💡 **typeSafe?** <br/>
-> I18nStore is type-safe by default. So, basically, you can't add the translation data that is not defined in the locale Json files. However, for fast development, you can off the typeSafe option manually.
+> I18nStore doesn't enforce adherence to your locale JSON definitions by default. This means that you can add translation data even if it isn’t pre-defined in your locale JSON files. However, if you prefer to enforce strict type-safety, you can manually enable the typeSafe option which allows you to notice the auto-completed list in translation data.
 >
 > ```tsx
-> // typeSafe: false
+> // typeSafe: true
 > const YourComponent = () => {
->   // can accept any string sheet title.
+>   // "useTranslation" shows the autocompletion suggestions
 >   const { t } = useTranslation('header');
 >
 >   return (
 >     <div>
->       {/* "t" function will accept and return any string */}
+>       {/* "t" function shows the autocompletion suggestions */}
 >       <button>{t('login')}</button>
 >     </div>
 >   );
@@ -877,10 +877,10 @@ sheet-i18n register --scope total
 
 </br>
 
-### 📄 export
+### 📄 import
 
 ```shell
-npx sheet-i18n export
+npx sheet-i18n import
 ```
 
 Exports translation data from Google Sheets to local export directory.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheet-i18n",
-  "version": "1.4.0-canary.5",
+  "version": "1.4.0-canary.6",
   "repository": {
     "type": "git",
     "url": "https://github.com/chltjdrhd777/sheet-i18n"
@@ -36,13 +36,13 @@
   },
   "license": "ISC",
   "dependencies": {
-    "@sheet-i18n/importer": "1.4.0-canary.3",
-    "@sheet-i18n/react": "1.1.0-canary.5"
+    "@sheet-i18n/react": "1.1.0-canary.6",
+    "@sheet-i18n/importer": "1.4.0-canary.4"
   },
   "devDependencies": {
     "tsup": "^6.0.0",
     "typescript": "^5.0.0",
-    "@sheet-i18n/typescript-config": "1.4.0-canary.3"
+    "@sheet-i18n/typescript-config": "1.4.0-canary.4"
   },
   "scripts": {
     "build": "tsup",