MickaelOnTheWave / MickaelOnTheWave/InvoiceManager
Refactor InvoiceDbController
Open
Refactor
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Separate it into several classes. Suggestion :
- One for direct interaction with DB and basic data return in C++ structures
- One for business logic (handling only C++ structures)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating InvoiceDbController and tracing which methods directly access the database versus handling business logic. Separate those responsibilities into classes that exchange C++ structures, then verify that the GUI client still performs its existing invoice operations correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100