feat: add move task to collection endpoint#3
Open
ehippy wants to merge 1 commit into
Open
Conversation
- Add POST /tasks/{uuid}/move endpoint to move tasks between collections
- Supports moving to inbox, today, upcoming, someday, anytime, or projects
- Adds TaskMove Pydantic model for request body
- Adds 7 tests covering move endpoint (auth, collection routing, project targets)
- Updates README with feature list, endpoint docs, and usage example
- Adds pytest/httpx as optional test dependencies
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Motivation
The API had full read/write support for tasks but was missing a way to move tasks between collections — a key capability for automations and integrations. For example, an automation could receive a notification and move a task from inbox to today, or from today to a specific project.
Test Plan