Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

POST /tasks/{id}/move with section_id silently strips parent_id from subtasks

未关闭
#258 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
api

调研方向

Locate the implementation and tests for POST /api/v1/tasks/{task_id}/move, then reproduce the section_id path with a parent task and subtask. Compare it with the parent_id path and add coverage showing that moving by section preserves the parent relationship or returns an explicit warning or error.

由索引模型根据 Issue 内容生成。

描述

Description

When moving a subtask to a section via POST /api/v1/tasks/{task_id}/move with {"section_id": "..."}, the API silently clears the task's parent_id, promoting the subtask to a top-level task. The response returns 200 with no warning that the parent relationship was removed.

Steps to reproduce

  1. Create a parent task and a subtask under it (parent_id set).
  2. Call POST /api/v1/tasks/{subtask_id}/move with body {"section_id": "<section_id>"}.
  3. Fetch the task again: parent_id is now null.

Expected behavior

Moving a subtask between sections should preserve its parent_id, or the API should return an error/warning if detaching the parent is intentional.

Actual behavior

The subtask is silently detached and becomes a top-level task in the target section.

Additional context

  • Moving with {"parent_id": "<parent_id>"} on the same endpoint does re-attach the task, so the move endpoint clearly understands parentage. Only the section_id variant drops it.
  • The task update endpoint (POST /api/v1/tasks/{task_id}) rejects parent_id as an unsupported field, so the move endpoint is currently the only way to restore the relationship after it is lost.
  • Observed against REST API v1 on 2026-09-22.
主要语言
Python
星标
250
派生
34
平均合并
2 天 1 小时
30 天内合并 PR
2

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Doist/todoist-api-python 的其他 Issue

查看 Doist/todoist-api-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。