@kong-ui-public/i18n 0.2.9-pr.150.1377068.0 → 0.2.9-pr.150.4b31da5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/dist/i18n.es.js +1 -1
- package/dist/i18n.es.js.map +1 -1
- package/dist/i18n.umd.js +1 -1
- package/dist/i18n.umd.js.map +1 -1
- package/dist/types/Translation.d.ts +1 -1
- package/dist/types/Translation.d.ts.map +1 -1
- package/dist/types/index.d.ts +1 -1
- package/dist/types/index.d.ts.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -247,7 +247,7 @@ And then, anywhere in application code where `i18n` is needed
|
|
|
247
247
|
|
|
248
248
|
#### With direct use of i18nT component
|
|
249
249
|
|
|
250
|
-
In some cases we do not have access to
|
|
250
|
+
In some cases we do not have access to the Vue `app` and cannot relay on registered i18nT plugin. Working on standalone components in `public-ui-components` is of those cases. And for this your component will look like:
|
|
251
251
|
|
|
252
252
|
|
|
253
253
|
```html
|
|
@@ -260,11 +260,11 @@ In some cases we do not have access to vue `app` and cannot relay on registered
|
|
|
260
260
|
</template>
|
|
261
261
|
|
|
262
262
|
<script setup lang="ts">
|
|
263
|
-
import { createI18n, Translation } from '@kong-ui-public/i18n'
|
|
263
|
+
import { createI18n, Translation, i18nTComponent} from '@kong-ui-public/i18n'
|
|
264
264
|
import english from './locales/en.json'
|
|
265
265
|
|
|
266
266
|
const i18n = createI18n('en-us', english)
|
|
267
|
-
const i18nT =
|
|
267
|
+
const i18nT = i18nTComponent(i18n)
|
|
268
268
|
|
|
269
269
|
</script>
|
|
270
270
|
|
package/dist/i18n.es.js
CHANGED