bderoo121 / bderoo121/journal-batch-processer
Purpose of "derived" set in _checkColumns?
Open
question
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The "derived" set is a group of "column names that won't prompt the user for input when updating." It isn't used anywhere except in instantiation. Is this a feature planned for the future?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating _checkColumns and inspect how the "derived" set is instantiated and whether it is referenced elsewhere. The issue does not define whether the set should be removed, documented, or made functional, so confirm the intended behavior with a maintainer before changing code; completion depends on that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100