Incorrect Update in Project (pyproject)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
There is an issue where the update logic is incorrectly impacting parts of the pyproject file. The update should only modify the version="XXX" field, but currently, it seems to be affecting other sections as well.
Steps to Reproduce:
1. Run `committy tag --bump-files` with a pyproject file.
2. Observe that fields other than version="XXX" are being updated unexpectedly.
Expected Behavior:
• Only the version="XXX" field in the **pyproject** file should be updated.
Actual Behavior:
• Other fields in the pyproject file are being altered, leading to unintended changes.
Tasks:
- [ ] Fix the logic to ensure only version="XXX" is updated.
- [ ] Add test cases to prevent regressions in the future.
Contributor 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.
Research direction
Reproduce the problem with `committy tag --bump-files` against a pyproject file and compare the resulting changes with the original. Trace the update logic responsible for pyproject handling, then add regression coverage showing that only the version="XXX" field changes; done means other fields remain untouched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100