MerginMaps / MerginMaps/work-packages
Option to drop some tables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
wp.py line 299
#TODO: drop tables that are not listed at all (?)
Suggestion - not listed tables should not be dropped. My thoughts about that... Let's assume we have a lot of tables, but a lot of them won't be filtered. We need all data (read only perhaps) for all users. It would be an overhead to list all tables. Let's assume that all data is needed.
- if I need some helper tables in main project for some reason, an option to drop that table in work packages should be added.
- If I need some helper or sketch tables in work packages, an option to exclude it from syncing back to main project should be added. Similar to #15
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
Start at wp.py line 299 and read the surrounding table-dropping and syncing behavior. Review the relationship to issue #15 and clarify whether the requested options control dropping tables, syncing them back, or both. Done requires agreed behavior and acceptance criteria for unlisted, helper, and sketch tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100