[Bay Dashboard] - Create List of Available Widgets
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in src/frontend/src/utils/bayDashboard.utils.tsx and inspect the existing dashboard widget types, sizes, and components referenced by the issue. Define the widget list for CALENDAR, OVERDUE_WORK_PACKAGES, TEXT_FIELD, and COUNTDOWN, then verify that getWidgetsForSize filters by size and getWidget returns the matching widget or undefined.
Written by the indexing model from the issue text.
Description
Description
On the frontend we want to create a list of every dashboard widget that exists and what sizes it can exist as. For example, the calendar widget could exist as a large widget or as a medium widget
In the future both the bay dashboard and the admin tools widget previews will read from this list
Acceptance Criteria
src/frontend/src/utils/bayDashboard.utils.tsx
- list of widgets
- getWidgetsForSize function that takes in a size and returns the widgets that can be that size
- getWidget function that takes in a widget type and returns that widget, or undefined
Proposed Solution
Create a const BAY_DASHBOARD_WIDGETS that is an array of all existing widgets
Create a widget interface with type, displayName, sizes, and the React component itself
{
type: BayDashboardWidgetType.CALENDAR,
displayName: 'Calendar',
sizes: [BayDashboardSlot.LARGE, BayDashboardSlot.MEDIUM],
component: CalendarWidget
}
Widgets to include
- CALENDAR
- OVERDUE_WORK_PACKAGES
- TEXT_FIELD
- COUNTDOWN
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 14
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.
More from Northeastern-Electric-Racing/FinishLine
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in Northeastern-Electric-Racing/FinishLine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·