Glossary term locale not covered
What the GlossaryTermLocaleNotCovered 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/glossary-term-locale-not-covered. See Errors and status codes for the shape every error shares.
Cannot save "<text>". Its locale "<locale>" is not one this glossary covers (<sourceCoverage>). Use one of those locales, or add this one to the glossary's source coverage.
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 |
|---|---|
text | string |
locale | string |
sourceCoverage | string[] |
Example #
json
{
"detail": "Cannot save \"<text>\". Its locale \"<locale>\" is not one this glossary covers (<sourceCoverage>). Use one of those locales, or add this one to the glossary's source coverage.",
"text": "<text>",
"locale": "<locale>",
"sourceCoverage": [
"<sourceCoverage>"
],
"type": "https://lingo.dev/docs/api/errors/glossary-term-locale-not-covered",
"status": 422,
"title": "Glossary term locale not covered"
}Returned by #
PATCH /v2/glossaries/{glossaryId}/terms/{id}POST /v2/glossaries/{glossaryId}/termsPOST /v2/glossaries/{glossaryId}/terms/create-many