Releases: seek-oss/vocab
@vocab/[email protected]
Patch Changes
- Updated dependencies [
09b7179
]:- @vocab/[email protected]
@vocab/[email protected]
Patch Changes
- Updated dependencies [
09b7179
]:- @vocab/[email protected]
@vocab/[email protected]
Minor Changes
-
09b7179
#154 Thanks @askoufis! - AddTranslationKeys
typeThe
TranslationKeys
type can be used to get a string literal union of all the translation keys used in a translation file.EXAMPLE USAGE
// .vocab/en.translations.json { "Hello": { "message": "Hello" }, "Goodbye": { "message": "Goodbye" } }
After running
vocab compile
:import type { TranslationKeys } from '@vocab/core'; import translations from './.vocab'; // 'Hello' | 'Goodbye' type Keys = TranslationKeys<typeof translations>;
@vocab/[email protected]
Patch Changes
- Updated dependencies [
09b7179
]:- @vocab/[email protected]
- @vocab/[email protected]
@vocab/[email protected]
Patch Changes
-
45cd995
#152 Thanks @askoufis! - Upload translations in a separate file per languageFixes a regression introduced when support for Phrase tags was added.
Part of adding support for tags involved swapping to uploading translations in a CSV file instead of a JSON file.
This had the unintended (and undocumented) side-effect of creating missing languages in the target Phrase project.
This is unnecessary in the case where the language doesn't actually have any translations and/or derives its translations from a parent language.
Only languages that actually have translations (i.e. they have messages defined in atranslations.json
file) will be created in the target Phrase project.
@vocab/[email protected]
Patch Changes
- Updated dependencies [
45cd995
]:- @vocab/[email protected]
@vocab/[email protected]
@vocab/[email protected]
Patch Changes
- Updated dependencies [
c0459e0
]:- @vocab/[email protected]
@vocab/[email protected]
Patch Changes
- Updated dependencies [
4e3c2f9
]:- @vocab/[email protected]
@vocab/[email protected]
Patch Changes
- Updated dependencies [
4e3c2f9
]:- @vocab/[email protected]