avo-hq/avo

Dashboard Ranges to control Card Ranges

Open

#2,071 opened on 2023年11月30日

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

説明

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

コントリビューターガイド

技術スタック
rubyrailshtmlcssjavascript
領域
full stack
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Ruby on RailsAvo gem basicsDashboard and card concepts
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
65
調査方針
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.