input.wrong_concept
An input is not the declared concept
| Type | https://mthds.ai/errors/input.wrong_concept |
| Family | input: A run's inputs. |
| Domain | input: the caller acts, by changing the request or its inputs |
| Retry | no: repeating the operation fails the same way |
| HTTP status | 422 |
| Raised as | a problem document, sent as the body of an HTTP response or kept in a run's record |
What it means
An input names or holds a concept that the method does not accept there, an unknown concept included.
What to do
Give the input as the concept the method declares, or as one that refines it. A stuff names its concept by its crate key, in its concept member.
Next steps
A problem carries the step aimed at whoever reads it: the first when its reader is the domain's actor, the caller, and the second for any other reader.
| Reader | Kind | Detail |
|---|---|---|
| The domain's actor | change_input |
Give the input '{input}' as '{expected}', then send the request again. |
| Any other reader | change_input |
Pass this to the caller, who must give the input '{input}' as '{expected}'. |
Detail
The problem's detail is written from this template, filled with the occurrence's parameters:
The input '
{input}' is given as '{provided}', but the method accepts '{expected}' there.
Parameters
Every parameter is present on every occurrence of the code.
| Name | Type | Description |
|---|---|---|
input |
identifier |
The input at fault. |
expected |
identifier |
The concept the method accepts for the input. |
provided |
identifier |
The concept the request gives. |
See also
- Stuffs on the wire
- Error Registry, which describes the members of this page
- Error Codes, every code of the core registry