Replace pydantic v1 `.dict()` with `.model_dump()` in the API
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 92/100
Research direction
Start with taskuary/server.py and run grep -n "\.dict()" taskuary/server.py to review the ten request-body call sites. Replace the listed v1 calls and add or run tests/test_no_pydantic_v1.py, then verify with python -m pytest -q that no targeted .dict() calls remain and the suite passes.
Written by the indexing model from the issue text.
Description
We require pydantic>=2, but taskuary/server.py still calls the v1 method body.dict() in ten places. Each call logs PydanticDeprecatedSince20: The dict method is deprecated; use model_dump instead, and it stops working in pydantic v3.
Where: grep -n "\.dict()" taskuary/server.py - ten hits (task create/update, split, calendar prep, fixtures, three settings-style updates).
Done when each is .model_dump() and the suite passes.
Test - a small tests/test_no_pydantic_v1.py that scans taskuary/server.py for .dict() called on request bodies (body.dict(, .second.dict(, .first.dict() and fails if any remain.
Getting started: pip install -e ".[dev]", then python -m pytest -q (offline, a few seconds). UI work: cd website && npm ci && npm test. See CONTRIBUTING.md. One small PR with the change and its test is perfect.
- Dominant language
- Python
- Stars
- 116
- Forks
- 22
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 11
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ldbumble/taskuary
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
ldbumble/taskuary#70 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
All issues in ldbumble/taskuary
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day