Back-end: PATCH /apartments/:id/visit/:visitId #244
Comments
|
Time estimation: 2 hours |
|
Actual time: 0.5 hour |
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
Back-end: Created GET /apartments/visit/actions Back-end: Created GET /apartments/visit/statuses Back-end: Created PATCH /apartments/:id/visit/:visitId This commit includes the relevant routes for the apartment visits feature: PUT /apartments/:id/visit - adds a new visit Back-end: GET /apartments/visit/actions - retrieves all supported statuses "movements" according to the business logic Back-end: Create GET /apartments/visit/statuses - retrieves all supported statuses of the system Back-end: PATCH /apartments/:id/visit/:visitId - for modification of an existing visit. #242, #243, #244, #250
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
This commit is the second one (and the last planned one) related to this issue and includes tests for the routes that were added as part of the visits feature: PUT /apartments/:id/visit - adds a new visit Back-end: GET /apartments/visit/actions - retrieves all supported statuses "movements" according to the business logic Back-end: Create GET /apartments/visit/statuses - retrieves all supported statuses of the system Back-end: PATCH /apartments/:id/visit/:visitId - for modification of an existing visit. #242, #243, #244, #250, #241
Open
|
Done on back-end side. The future of the feature should be decided. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The route is going to be used for modifying an existing visit relevant to the current registered user (he is the visitor or the owner) to a certain apartment.
Expects to get the time of the visit under "schedTo" property and the new status of the visit under "status" property as part of the request body.
The text was updated successfully, but these errors were encountered: