yata-fetch 2.0.1 → 2.0.2
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/.eslintrc.json +2 -1
- package/.github/workflows/test.yaml +3 -0
- package/.husky/commit-msg +4 -0
- package/README.md +33 -12
- package/commitlint.config.cjs +1 -0
- package/package-lock.json +8563 -0
- package/package.json +4 -1
package/.eslintrc.json
CHANGED
package/README.md
CHANGED
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
# yata-fetch
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
 [](https://www.npmjs.com/package/yata-fetch)   
|
|
4
|
+
|
|
5
|
+
Welcome to Yata integration package, this package will allow you to easy get your translations from [Yata](https://run.yatapp.net/) service.
|
|
4
6
|
|
|
5
7
|
## Installation
|
|
6
8
|
|
|
@@ -23,7 +25,7 @@ You can check token in your organization settings.
|
|
|
23
25
|
|
|
24
26
|
Example `.yata.json` file:
|
|
25
27
|
|
|
26
|
-
```
|
|
28
|
+
```json
|
|
27
29
|
{
|
|
28
30
|
"token": "MY_YATA_API_TOKEN",
|
|
29
31
|
"project": "XXX",
|
|
@@ -68,7 +70,7 @@ Hint:
|
|
|
68
70
|
|
|
69
71
|
It's best to create scripts for generating translations in `package.json` file. For example:
|
|
70
72
|
|
|
71
|
-
```
|
|
73
|
+
```json
|
|
72
74
|
"scripts": {
|
|
73
75
|
"yata-fetch": "yata-fetch --config .yata.json"
|
|
74
76
|
"yata-fetch:en": "yata-fetch --config .yata.json --locale en_US"
|
|
@@ -79,25 +81,44 @@ and simply call with `npm run yata-fetch`
|
|
|
79
81
|
|
|
80
82
|
## Problems?
|
|
81
83
|
|
|
82
|
-
|
|
84
|
+
If you find some problems or bug in the package please open an Issue.
|
|
83
85
|
|
|
84
|
-
##
|
|
86
|
+
## Collaboration
|
|
85
87
|
|
|
86
|
-
|
|
88
|
+
Want help to develop this package? Please open a Pull Request.
|
|
87
89
|
|
|
88
90
|
## Package Maintenance
|
|
89
91
|
|
|
90
92
|
### Installation
|
|
91
93
|
|
|
92
|
-
|
|
93
|
-
|
|
94
|
+
```
|
|
95
|
+
git clone <this repository>
|
|
96
|
+
npm install
|
|
97
|
+
```
|
|
94
98
|
|
|
95
|
-
|
|
99
|
+
### Running Tests
|
|
96
100
|
|
|
97
|
-
|
|
101
|
+
```
|
|
102
|
+
npm run test
|
|
103
|
+
```
|
|
98
104
|
|
|
99
105
|
### Building
|
|
100
106
|
|
|
101
|
-
|
|
107
|
+
```
|
|
108
|
+
npm run build
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
### Release
|
|
112
|
+
|
|
113
|
+
```
|
|
114
|
+
npm version <major|minor|patch>
|
|
115
|
+
git push origin --tags
|
|
116
|
+
```
|
|
117
|
+
Optionally create new release entry in Github Releases.
|
|
118
|
+
When Github Action detect new version there will be automatic release to NPM.
|
|
119
|
+
|
|
120
|
+
## License
|
|
121
|
+
|
|
122
|
+
[MIT](https://opensource.org/licenses/MIT)
|
|
102
123
|
|
|
103
|
-
|
|
124
|
+
Copyright (c) 2017-present, Dominik Zborowski
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
module.exports = {extends: ['@commitlint/config-conventional']}
|