avo-hq/avo

Dashboard Ranges to control Card Ranges

Open

#2,071 opened on Nov 30, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Ruby (1,778 stars) (308 forks)user submission
Back endEnhancementFront endHelp wanted

Description

Feature

Ability to control Card.ranges from Dashboard.ranges. It is common to have multiple cards on a dashboard that will have a range. Often times that range is the same for all card. For example, if I'm looking at various sales/order numbers, I want them all for the same time period ( month, week, quater, year-to-date, etc) . Screenshot really explains it much better

Current workarounds

Just using one big PartialCard, with multiple queries generating a Hash that's being fed to the card for displaying

Screenshots or screen recordings

dashboard

Contributor guide

Tech stack
rubyrailshtmlcssjavascript
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Ruby on RailsAvo gem basicsDashboard and card concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the avo source code to understand how Dashboard and Card models handle ranges. Look at the Dashboard model and its relationship to Cards. Determine how to propagate a dashboard level range to all its cards, possibly by adding a method that sets each card's range attribute when the dashboard range is updated. Review any existing tests for dashboard and card ranges to ensure compatibility.