33 fetch and move tasks #69
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
setup & create task, category
sorry, updated this after I pushed so just gonna change it here too
Create label entity and corresponding migration
Mn 15/setup and seeding
…ndling and write tests
add npm run test
Create CODEOWNERS
24 Create 4 Boxes
AA-6: Edit Task Route
implemented/tested delete_labels route
Increased responsiveness by positioning the task title and due date text relative to each other (instead of using absolute positioning)
AA-25: Create Task
8 label route
add_labels endpoint implemented/tested
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ℹ️ Issue
Closes https://github.com/Code-4-Community/jumpstart/issues/33
📝 Description
For this ticket, I integrated the frontend and backend, allowing us to get all tasks from the backend and now properly display them in the frontend. Additionally, I implemented drag-and-drop functionality to allow tasks to be moved from one box to another. This is done by adding draggable properties to each of the tasks, and putting proper functionality in the parent component (the task box as a whole) to monitor the task id that was being moved, and the new box (category) it was being moved to. This gives us all the information we need to make an update call to the backend.
Briefly list the changes made to the code:
✔️ Verification
I verified proper drag-and-drop functionality with tasks, as well as appropriate updating in backend.
Screen recording of moving tasks:
https://github.com/user-attachments/assets/1e59ca59-a6f1-42b0-993a-eec27c077474
Backend update:
