Source and translations edited together
What the StudioProposalMixesSourceAndTranslations error (422 Unprocessable Content) means, the fields it carries, and the endpoints that return it.
The API answers 422 Unprocessable Content with this problem. Its type is https://lingo.dev/docs/api/errors/studio-proposal-mixes-source-and-translations. See Errors and status codes for the shape every error shares.
This proposal edits both the source and translations of <type> / <id>. The next translation run would replace the edited translations, so send the source edits and the translation edits in separate proposals.
Fields #
Besides the standard type, status, title and detail members, the body carries these fields. The detail text is built from them, so a client can show its own text instead.
| Field | Type |
|---|---|
document | object |
document.scopeKey | string |
document.type | string |
document.id | string |
Example #
json
{
"detail": "This proposal edits both the source and translations of <type> / <id>. The next translation run would replace the edited translations, so send the source edits and the translation edits in separate proposals.",
"document": {
"scopeKey": "<scopeKey>",
"type": "<type>",
"id": "<id>"
},
"type": "https://lingo.dev/docs/api/errors/studio-proposal-mixes-source-and-translations",
"status": 422,
"title": "Source and translations edited together"
}