lokalise / node-lokalise-api / 32851934426

100%

push

github

MET-2115 Add translation_engine to task creation params (#582)

* MET-2115 Add translation_engine to task creation params

An `automatic_translation` task is performed by Lokalise AI by default. The API
also accepts a `translation_engine` of `google` or `deepl` to have a machine
translation engine do it instead, but `CreateTaskParams` had no field for it, so
callers had to cast to get it into the request body.

The parameter is create-only - `PUT /tasks/{id}` does not accept it - so it is
added to the `Omit` list in `UpdateTaskParams` rather than inherited.

The response does not echo the engine, so the new test asserts through the
stubbed request body instead. Its fixture reflects what an MT task returns: the
synthetic per-language assignee is the Lokalise Support representation, where an
AI-engine task returns Lokalise AI.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* MET-2115 Drop the base-language restriction from the MT docs

The pair validation on the API is source-parameterized, so a machine translation
task does not need the project base language as its source. The restriction is
being removed from the API rather than documented here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Clarify that automatic_translation refers to the translation, not the task

The previous wording ("To have the task translated automatically") read as
though the task itself was created automatically. Reframe the paragraph
around the actual choice: a manual `translation` task delegated to assigned
translators, versus an `automatic_translation` task performed by an
automation.

Also name the `translation_engine` values explicitly. The old copy implied
that passing `translation_engine` selected machine translation, but `ai` is
itself a valid value of that parameter, so MT is selected by the `google` /
`deepl` values rather than by the parameter's presence.

Scope the opening to translation tasks, since `review` and `lqa_... (continued)

193 of 193 branches covered (100.0%)

Branch coverage included in aggregate %.

562 of 562 relevant lines covered (100.0%)

28.74 hits per line