MerginMaps / MerginMaps/work-packages
Only accept changes from work packages if they pass the filter
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently we are accepting all changes from work packages. We should probably test whether inserted/updated rows from a work package would pass the filtering. If not, we would reject such changes. Any rejected changes would need to be stored somewhere in the master Mergin project. There is a risk with rejections that the invalid edits could be unintended (e.g. the "team" column value would be NULL instead of the expected). Another option would be that instead of rejecting such edits, we would modify such insert/update statements to pass the filtering.
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
No files, tests, or entry points are named. Trace how work-package insert and update statements are applied to the master Mergin project, then determine whether rejected changes should be stored or edits should be modified to pass filtering. Done requires an agreed behavior for invalid edits and coverage of the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100