@transifex/api 2.2.0-alpha.0 → 2.3.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/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
A javascript SDK for the [Transifex API (v3)](https://transifex.
|
|
1
|
+
A javascript SDK for the [Transifex API (v3)](https://developers.transifex.com/reference)
|
|
2
2
|
|
|
3
3
|
## Intro
|
|
4
4
|
|
|
@@ -85,7 +85,7 @@ await projects.fetch();
|
|
|
85
85
|
```
|
|
86
86
|
|
|
87
87
|
However, if you look at how a project is represented in the
|
|
88
|
-
[API docs](https://transifex.
|
|
88
|
+
[API docs](https://developers.transifex.com/reference/get_projects-project-id),
|
|
89
89
|
Organization objects have a `projects` relationship with a `related` link, so
|
|
90
90
|
you can achieve the same thing with:
|
|
91
91
|
|
|
@@ -95,7 +95,7 @@ await projects.fetch();
|
|
|
95
95
|
```
|
|
96
96
|
|
|
97
97
|
If you look into the
|
|
98
|
-
[API docs](https://transifex.
|
|
98
|
+
[API docs](https://developers.transifex.com/reference/get_projects),
|
|
99
99
|
you can see that a `slug` filter is also supported, so to find a specific
|
|
100
100
|
project, you can do:
|
|
101
101
|
|
|
@@ -184,7 +184,7 @@ await project.change('team', team_2);
|
|
|
184
184
|
```
|
|
185
185
|
|
|
186
186
|
This will send a PATCH request to
|
|
187
|
-
[`/projects/XXX/relationships/team`](https://transifex.
|
|
187
|
+
[`/projects/XXX/relationships/team`](https://developers.transifex.com/reference/patch_projects-project-id-relationships-team)
|
|
188
188
|
to perform the change. Again, you should consult the API documentation to see
|
|
189
189
|
which relationships can be changed and with which methods (in this case -
|
|
190
190
|
changing a project's team - both methods are available).
|