sillsdev / sillsdev/TheCombine
Refactor Data Entry to separate TreeView from DataEntry table
Open
Nobody has claimed this yet.
frontend
maintenance
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 10
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 9
Description
The DataEntry page should display either the TreeView for a domain or the Data Entry Table. Currently, the knowledge of whether the TreeView is displayed is in the DataEntryTable; it should be moved up a level to the DataEntry page.
Contributor guide
No contributing guide indexed for this repository
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
Locate the DataEntry page, DataEntryTable, and TreeView components, then trace where the table currently decides whether TreeView is displayed. Move that decision to DataEntry so the page selects either TreeView for a domain or the Data Entry Table, while preserving the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100