yata-fetch v2.1.5
yata-fetch
Welcome to Yata integration package, this package will allow you to easy get your translations from Yata service.
Installation
yarn add yata-fetch -D
npm install yata-fetch -D
Usage
Setup
- Create config file in project folder (see details below).
- Add
MY_YATA_API_TOKENkey to env variables in.zshrc/.bashrc:
export MY_YATA_API_TOKEN=XXXXYou can check token in your organization settings.
Configuration file
Example .yata.json file:
{
"token": "MY_YATA_API_TOKEN",
"project": "XXX",
"locales": ["en_US", "de_DE"],
"format": "yml",
"root": false,
"outputPath": "./translations",
"strip_empty": true
}token(string, required) - name of ENV variable containing API tokenproject(string, required) - ID of the project, you can get it from your organization settings in Yatalocales(array, required) - locales to generateformat(string, optional, default: yml) - output file formatroot(boolean, optional, default: false) - if set totruelocale file will contain locale as root elementoutputPath(string, optional, default: './translations') - path where files will be generatedstrip_empty(boolean, optional, default: false) - if set totrueparser will omnit empty keys from generation and export only those that have text
Fetching translations
$ yata-fetch [options]Options:
config(string, optional, default: yata.json) - path to json config file.locale- if you like you can generate only one locale instead whole stack from config file
Example:
$ yata-fetch --config .yata.json --locale en_USIt's recommended to create scripts for generating translations in package.json file. For example:
"scripts": {
"yata-fetch": "yata-fetch --config .yata.json"
"yata-fetch:en": "yata-fetch --config .yata.json --locale en_US"
}and simply call with yarn yata-fetch or npm run yata-fetch
Problems?
If you find some problems or bug in the package please open an Issue.
Collaboration
Want help to develop this package? Please open a Pull Request.
Package Maintenance
Installation
git clone <this repository>
yarn installRunning Tests
yarn testBuilding
yarn buildUpgrading
yarn upgrade-interactiveRelease
npm version <major|minor|patch>
git push origin --tagsOptionally create new release entry in Github Releases. When Github Action detect new version there will be automatic release to NPM.
License
Copyright (c) 2017-present, Dominik Zborowski
3 years ago
3 years ago
3 years ago
3 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
5 years ago
5 years ago
5 years ago
6 years ago
7 years ago
7 years ago
7 years ago
7 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago