Conversation
…ters - Added `help` tooltips to `factor_window`, `vol_window`, `adv_pct`, `vol_q_high`, `bt_cost`, `dd_alert`, `vol_alert`, `beta_alert`, and `dttl_alert` parameters in `src/dashboard.py` to provide concrete examples and improve UX. - Added a UX learning entry to `.Jules/palette.md` specifying that inputs involving statistical or financial parameters should include concrete examples in their tooltips. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
…ters - Added `help` tooltips to `factor_window`, `vol_window`, `adv_pct`, `vol_q_high`, `bt_cost`, `dd_alert`, `vol_alert`, `beta_alert`, and `dttl_alert` parameters in `src/dashboard.py` to provide concrete examples and improve UX. - Formatted the updated lines to match `black` style constraints to fix CI failures. - Added a UX learning entry to `.Jules/palette.md` specifying that inputs involving statistical or financial parameters should include concrete examples in their tooltips. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
…ters - Added `help` tooltips to `factor_window`, `vol_window`, `adv_pct`, `vol_q_high`, `bt_cost`, `dd_alert`, `vol_alert`, `beta_alert`, and `dttl_alert` parameters in `src/dashboard.py` to provide concrete examples and improve UX. - Formatted the updated lines to match `black` style constraints to fix CI failures. - Added a UX learning entry to `.Jules/palette.md` specifying that inputs involving statistical or financial parameters should include concrete examples in their tooltips. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
…ters - Added `help` tooltips to `factor_window`, `vol_window`, `adv_pct`, `vol_q_high`, `bt_cost`, `dd_alert`, `vol_alert`, `beta_alert`, and `dttl_alert` parameters in `src/dashboard.py` to provide concrete examples and improve UX. - Formatted `src/dashboard.py` to comply perfectly with the project's `black` constraints so the CI `black --check src/` check passes for this file (resolving the previous GitHub Actions CI test failure). - Added a UX learning entry to `.Jules/palette.md` specifying that inputs involving statistical or financial parameters should include concrete examples in their tooltips. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
💡 What: Added
helptooltips to 9 statistical and financial input parameters in the sidebar. Also created.Jules/palette.mdto document the UX learning.🎯 Why: Parameters like "Factor Beta Window" and "Transaction Cost (bps)" are much clearer when concrete examples are provided in tooltips (e.g., "63 days ≈ 3 months", "10 bps = 0.10%"). This makes the interface more intuitive and accessible, following Palette's UX principles.
📸 Before/After: Visual changes verified via Playwright screenshot.
♿ Accessibility: Improved form clarity by providing context without cluttering the UI.
PR created automatically by Jules for task 15601036801549067990 started by @aarjava