Conversation
…ers via tooltips Adds tooltips with concrete examples to various statistical and financial input parameters in the sidebar to reduce user ambiguity. Also adds a journal entry to `.Jules/palette.md` to document this critical UX learning. 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. |
- Add `help` tooltips with concrete examples to `bt_cost`, `factor_window`, `vol_window`, `adv_pct`, and `vol_q_high` inputs in the sidebar - Formats inline to ensure compliance with Black styling - Add UX learning regarding tooltip necessity for financial params to `.Jules/palette.md` Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
- Refactored multiline edits in `src/dashboard.py` to be compliant with `black` formatting - Ensured `black --check src/dashboard.py` passes successfully - Validated test suite passes with `pytest tests/` Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
- Formatted all Python files in `src/` and `tests/` using `black` to comply with the strict CI checks defined in `.github/workflows/ci.yml`. - `black --check src/ tests/` now passes cleanly. - `pytest tests/` continues to pass locally. Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
1 participant
💡 What: Added tooltips with concrete examples (using the
helpparameter) to financial and statistical inputs (bt_cost,adv_pct,vol_q_high,factor_window,vol_window) in the sidebar.🎯 Why: Statistical and financial parameters like basis points or percentiles are often ambiguous to users. Adding concrete examples (e.g., "10 bps = 0.10%") significantly improves clarity and reduces errors.
♿ Accessibility: Improves cognitive accessibility by providing concrete context for abstract parameters.
📸 Before/After: See generated Playwright screenshots (e.g.,
vol_window_tooltip.png,bt_cost_tooltip.png).PR created automatically by Jules for task 3253469898301344781 started by @aarjava