We originally included it in T366181 but that didn't make sense because language codes in the request body aren't values, they're the keys in labels/descriptions/aliases. This applies to both language_code and site_id keys.
response code: 400
error code: invalid-key
message: "Invalid key '{key}' in '{json_pointer_to_parent}'"
context: { "path": "{json_pointer_to_parent}", "key": "{key}" }
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ifrahkhanyaree_WMDE | T369511 🔑 [Generalized error] invalid-key in request body | |||
| Resolved | Dima_Koushha_WMDE | T370780 🔑 Replace 'invalid-language-code' error with 'invalid-key' | |||
| Resolved | Dima_Koushha_WMDE | T370781 🔑 Replace `invalid-site-id` error with `invalid-key` |
Polishing - We don't think 'unexpected field' would work considering that it IS an expected field, just with an invalid value.
Another case that came up was for invalid-site-id (in the POST item)
We'd prefer keeping the original message for both
Refinement: Alt. generalized error that would fit both cases i.e., invalid language code and invalid site id. Error code to be "invalid-key" and error message TBD and HTTP error code will be 400.