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
Wouldn't it be a good idea to design the API as a REST API? I'd like to show this sample in REST trainings, but unfortunately, it does not fit the guidelines.
Main points are
URLs:
pets instead of pet, users instead of user
findByStatus and findByTags as parameters of GET /pets
image upload with PUT /pets/{petId}/image
Login/Logout (if done via the API) by using POST
(Wouldn't have any problem to provide a merge request, but maybe it is a conscious decision to NOT fit REST guidelines?)
The text was updated successfully, but these errors were encountered:
Wouldn't it be a good idea to design the API as a REST API? I'd like to show this sample in REST trainings, but unfortunately, it does not fit the guidelines.
Main points are
pets
instead ofpet
,users
instead ofuser
findByStatus
andfindByTags
as parameters ofGET /pets
PUT /pets/{petId}/image
POST
(Wouldn't have any problem to provide a merge request, but maybe it is a conscious decision to NOT fit REST guidelines?)
The text was updated successfully, but these errors were encountered: