Northeastern-Electric-Racing / Northeastern-Electric-Racing/Argos
[Epic] - Add graph screen integration with widgets
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 26
Description
Overview
This is a collection of all the tickets, and housing of the plan for rolling out clickable widgets.
Stakeholders
Product Stakeholder: TBD
Software Stakeholder: @bracyw
Reference Users: Max M. @jr1221
User Story
As a engineer, I want to be able to easily see historic data for live updated widgets, so that I can better diagnose the reasoning behind it's current value.
Success Metrics
- All widgets work as before, just with this added functionality.
- Users can click on a widget and it will bring them to the graph screen
Rollout Plan
We can roll this out slowly. The first ticket will be adding the foundational layout for how to migrate a widget to being clickable. Then we will slowly implement widget by widget (or in groups depending on member availability). There should be a large focus on abstraction and general code quality improvements and reuse during this process. THIS IS A PERFECT OPPURTUNITY FOR UPPING OUR OVERALL WIDGET CODE STANDARDS. <- meaning if you see some random widget that has shitty code, fix it (it doesn't have to be part of adding the clickable functionality, that's the easy part)
Out of Scope
- Supporting clicking anywhere on the widget (there are some widgets who have graphs on them, clicking on the graph does not have to bring you to the graph page)
- Combining multiple widgets into one click (although this is something that we could think of during initial impl, as a possible future extension.)
Background / Context
There have been requests to allow widgets, or rather displays of certain numbers on our dashboards, to be clickable... which will bring the user to the graph screen which will graph the given topic(s). Along with that we will also add on hover a showing of the topic(s) associated with the widget.
Acceptance Criteria & Mock-ups
TBD
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
The issue names no files, tests, or entry points; start by identifying the dashboard widget and graph-screen components, then break the rollout plan into a foundational ticket and widget-specific work. Done means the scope and acceptance criteria are defined, each widget can navigate to the appropriate graph view, and existing widget behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100