Skip to content

Releases: seek-oss/vocab

@vocab/phrase@1.3.1

13 Nov 21:58
7f8687a
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [8228608]:
    • @vocab/core@1.6.0

@vocab/core@1.6.0

13 Nov 21:58
7f8687a
Compare
Choose a tag to compare

Minor Changes

@vocab/cli@1.4.1

13 Nov 21:57
7f8687a
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [8228608]:
    • @vocab/core@1.6.0
    • @vocab/phrase@1.3.1

@vocab/webpack@1.2.4

30 Oct 02:33
914a00f
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [161d698]:
    • @vocab/core@1.5.0

@vocab/types@1.3.3

30 Oct 02:33
914a00f
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [161d698]:
    • @vocab/core@1.5.0

@vocab/react@1.1.8

30 Oct 02:32
914a00f
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [161d698]:
    • @vocab/core@1.5.0

@vocab/phrase@1.3.0

30 Oct 02:32
914a00f
Compare
Choose a tag to compare

Minor Changes

  • 161d698 #170 Thanks @jasoncheng-jora! - vocab push and vocab pull can support global keys mapping. When you want certain translations to use a specific/custom key in Phrase, add the globalKey to the structure.

    EXAMPLE USAGE:

    // translations.json
    {
      "Hello": {
        "message": "Hello",
        "globalKey": "hello"
      },
      "Goodbye": {
        "message": "Goodbye",
        "globalKey": "app.goodbye.label"
      }
    }

    In the above example,

    • vocab push will push the hello and app.goodbye.label keys to Phrase.
    • vocab pull will pull translations from Phrase and map them to the hello and app.goodbye.label keys.
  • 161d698 #170 Thanks @jasoncheng-jora! - Add an optional errorOnNoGlobalKeyTranslation flag to pull function. If set to true, it will error if a translation is missing in Phrase for a translation with a global key.

    EXAMPLE USAGE:

    import { pull } from '@vocab/phrase';
    
    const vocabConfig = {
      devLanguage: 'en',
      language: ['en', 'fr'],
    };
    
    await pull(
      { branch: 'myBranch', errorOnNoGlobalKeyTranslation: true },
      vocabConfig,
    );

Patch Changes

  • Updated dependencies [161d698]:
    • @vocab/core@1.5.0

@vocab/core@1.5.0

30 Oct 02:32
914a00f
Compare
Choose a tag to compare

Minor Changes

  • 161d698 #170 Thanks @jasoncheng-jora! - vocab push and vocab pull can support global keys mapping. When you want certain translations to use a specific/custom key in Phrase, add the globalKey to the structure.

    EXAMPLE USAGE:

    // translations.json
    {
      "Hello": {
        "message": "Hello",
        "globalKey": "hello"
      },
      "Goodbye": {
        "message": "Goodbye",
        "globalKey": "app.goodbye.label"
      }
    }

    In the above example,

    • vocab push will push the hello and app.goodbye.label keys to Phrase.
    • vocab pull will pull translations from Phrase and map them to the hello and app.goodbye.label keys.

@vocab/cli@1.4.0

30 Oct 02:32
914a00f
Compare
Choose a tag to compare

Minor Changes

  • 161d698 #170 Thanks @jasoncheng-jora! - Error on no translation for global key

    By default, vocab pull will not error if a translation is missing in Phrase for a translation with a global key.
    If you want to throw an error in this situation, pass the --error-on-no-global-key-translation flag:

    EXAMPLE USAGE:

    vocab pull --error-on-no-global-key-translation

Patch Changes

  • Updated dependencies [161d698, 161d698]:
    • @vocab/phrase@1.3.0
    • @vocab/core@1.5.0

@vocab/webpack@1.2.3

25 May 06:07
f171113
Compare
Choose a tag to compare

Patch Changes

  • Updated dependencies [09b7179]:
    • @vocab/core@1.4.0