String-based API support #214
Assignees
Labels
Comments
andrii-bodnar
added
enhancement
|
Hi @andrii-bodnar, I would like to try implementing this as well. |
|
Hi @Zahid92, awesome, thank you! Assigning it to you. Feel free to contact me here if you have any questions. |
|
Hi @Zahid92 do you have any updates on this? |
|
Sorry, I got busy with some personal stuff. |
|
Hi @andrii-bodnar in ListLabels isSystem is an enum for {0, 1}. |
|
Hi @Zahid92, well, nice question :) For some unknown reason it was implemented this way, but it's actually better to have the boolean type here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Crowdin has recently released a new type of projects - String-based.
In string-based projects, the focus is on managing translatable content as individual strings rather than source files. In this project type, after uploading source files, Crowdin parses them into source strings. Unlike file-based projects, source files aren’t stored, and the emphasis is on managing the content at the string level. This approach is beneficial when dealing with projects that involve continuous content updates, dynamic content, or where a string-oriented structure is preferred.
As a result, the API differs a bit from the file-based projects. Most of the endpoints are the same, but some endpoints have different parameters or return different responses, some endpoints are not available at all, and some new endpoints are available only for string-based projects.
We should update the API clients to support string-based projects as well.
Progress:
String-based support for (#224):
Remaining String-based support for:
References:
It has been implemented for the following clients:
The text was updated successfully, but these errors were encountered: