fortedigital / fortedigital/Optimizely.ContentUsage
Refactoring: separate common table components
Open
FE
- Dominant language
- C#
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Both ContentTypesView and ContentTypeUsageView includes duplicated Table structure.
I think we should reorganize and prepare common table structure with specific row definition for both views.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate ContentTypesView and ContentTypeUsageView, then compare their duplicated Table structures and row definitions. The work is done when a common table structure is used by both views while each retains its specific row definition and existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100