You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation states that the fields bookId and customerName are required when submitting a new order. However, I have tested the /orders endpoint and found that an order can be successfully created without providing the customerName.
Steps to Reproduce:
Send a POST request to the /orders endpoint without including the customerName field:
POST /orders/Authorization: Bearer <YOUR TOKEN>
{
"bookId": 1
}
Observe that the order is created successfully, even though the customerName is missing.
Check the created orders using the /orders endpoint to confirm the orders are listed without the customerName:
Expected Behavior: The API should return an error indicating that the customerName field is required.
Actual Behavior: The order is created without the customerName.
Additional Information: It would be helpful to update the documentation to reflect the actual behavior of the API. You can find the documentation here.
The text was updated successfully, but these errors were encountered:
The documentation states that the fields
bookId
andcustomerName
are required when submitting a new order. However, I have tested the/orders
endpoint and found that an order can be successfully created without providing thecustomerName
.Steps to Reproduce:
Send a POST request to the
/orders
endpoint without including thecustomerName
field:Observe that the order is created successfully, even though the
customerName
is missing.Check the created orders using the
/orders
endpoint to confirm the orders are listed without thecustomerName
:Expected Behavior: The API should return an error indicating that the
customerName
field is required.Actual Behavior: The order is created without the
customerName
.Additional Information: It would be helpful to update the documentation to reflect the actual behavior of the API. You can find the documentation here.
The text was updated successfully, but these errors were encountered: