Improve API (API 1.1) #421
Conversation
The other endpoints use 'Invalid ID' to signify either missing or invalid. This endpoint used to use 'Invalid Username' to signify that the member does not exist, while the other's would've used 'Member not found' for that.
There's an inconsistency in whether to call a member a user. Generally, users are the ones with admin access, while members are the customers.
krestenlaust
force-pushed
the
improve-api
branch
from
0a51575
to
1b2a2e5
Compare
Even though it's a bool, I believe it's more appropriate to keep the naming consistent with non-bool return types. Also, it still returns an object.
I won't rename the actual endpoint because of backwards compatibility.
|
QR-endpoint apparently uses Stregdollars as opposed to Stregøre. I feel like streamlining this is too big a change. |
|
|
More meaningful response in Active Products-endpoint, now returns {"1":
{"name": "Beer", "price": 600}}, instead of {"1": ["Beer", 600]}
|
Changed response format for Active Products-endpoint: Instead of |
|
Changed format for Category_mapping endpoint output: Much more verbose, but it's more like the other endpoints. Considering changing it to not return products which don't have any mapped categories |
#420 aims to document the API. This PR addresses inconsistencies found during that documentation effort. Both in implementation and in the actual API.
It increments the API versioning to 1.1