Change Details

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. The message would say "Invalid value at '/item/labels/bad-language-code'" which doesn't fit. Possible options: keep as is or consider it a generic "unexpected field".

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}" }`

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. The message would say "Invalid value at '/item/labels/bad-This applies to both `language-_code'" which doesn't fit` and `site_id` keys. Possible options: keep as is or consider it a generic "unexpected field".response code: 400 error code: `invalid-key` message: `"Invalid key '{key}' in '{json_pointer_to_parent}'"` context: `{ "path": "{json_pointer_to_parent}", "key": "{key}" }`