Implement function to activate/deactivate planned scenario
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the existing planned-scenario API entry points and related tests in the Python client. Determine how scenario identifiers and target statuses are represented, then implement activation and deactivation while matching the existing API patterns. Done means callers can change a planned scenario’s status and the behavior is covered by tests.
Written by the indexing model from the issue text.
Description
Hello team ! In some use cases happy user of pyoverkiz would need to activate / desactivate a planned scenario. I don’t think this is doable with current version. It would be cool to have a method which takes a scenario identifier and a target status. Thanks !
- Dominant language
- Python
- Stars
- 58
- Forks
- 37
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 31
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 iMicknl/python-overkiz-api
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
iMicknl/python-overkiz-api#2273 · 5 comments ·
Maintainers usually reply within 5 days
All issues in iMicknl/python-overkiz-api
Similar issues
-
Atomic append fails to create a missing filePossibly taken @harbinresearcher claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fabiocaccamo/python-fsutil#201 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danparshall/claude_researcher#87 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
GhostManager/Ghostwriter#998 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
datajoint/datajoint-python#1586 ·
Maintainers usually reply within 1 day