-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ITG-111] Przystosować backend do nowej mechaniki dodawania i edycji zadań #54
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic looks alright so I think you can proceed to implementing the editing part
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, good job, i hope task editing will not be harder than that
…tions and subtasks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The API shape here doesn't match the one in #55. @bkulawska, @koszar91 please decide on a common format and implement it.
Only creation of tasks for now, let me know if the code is okay.
![image](https://user-images.githubusercontent.com/76395559/172070380-f84f4f6a-2975-4b7d-b383-28ba9b02194b.png)
I tested manually from postman and it seems to be working fine.
This is how I expect the frontend to deliver the content (for creation):
EDIT:
![image](https://user-images.githubusercontent.com/76395559/172705817-981512ee-4b4c-4772-b0ff-9054683339d1.png)
Added edition as well.
Tested manually from postman again and it seems to be working fine.
This is how I expect the frontend to deliver the content (for edition):
You can see there's no "subtasksToDelete" list - it's because this can be done by passing the relationId to "relationsToDelete" list and that will suffice.