Skip to content

🎨 Palette: Add explicit help tooltip to Transaction Cost input#99

Open
aarjava wants to merge 2 commits intomainfrom
palette/tooltip-transaction-cost-13893743599193846005
Open

🎨 Palette: Add explicit help tooltip to Transaction Cost input#99
aarjava wants to merge 2 commits intomainfrom
palette/tooltip-transaction-cost-13893743599193846005

Conversation

@aarjava
Copy link
Copy Markdown
Owner

@aarjava aarjava commented Apr 12, 2026

🎨 Palette: Add help tooltip to Transaction Cost input

πŸ’‘ What: Added a help tooltip to the "Transaction Cost (bps)" st.number_input widget.
🎯 Why: "Basis points (bps)" is a financial term that can be ambiguous without an explicit scale. The tooltip clarifies the unit (e.g., "10 bps = 0.10%") and its purpose ("Estimated execution drag per trade"), reducing cognitive load and making the application more intuitive.
β™Ώ Accessibility: This aligns with our UX standards by providing contextual help text directly attached to the input field, improving form usability.

All tests pass and formatting has been applied.


PR created automatically by Jules for task 13893743599193846005 started by @aarjava

To improve UX and align with accessibility standards, this commit adds a
`help` tooltip to the "Transaction Cost (bps)" `st.number_input` in
`src/dashboard.py`. The tooltip clarifies that "10 bps = 0.10%" and
explains its function as "Estimated execution drag per trade."

This change makes the financial terminology more intuitive for users and
ensures inputs involving statistical or financial parameters contain
concrete examples. All tests pass, and formatting conforms to Black
standards.

Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

πŸ‘‹ 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

To improve UX and align with accessibility standards, this commit adds a
`help` tooltip to the "Transaction Cost (bps)" `st.number_input` in
`src/dashboard.py`. The tooltip clarifies that "10 bps = 0.10%" and
explains its function as "Estimated execution drag per trade."

This change makes the financial terminology more intuitive for users and
ensures inputs involving statistical or financial parameters contain
concrete examples. All tests pass, and formatting conforms to Black
standards for the specifically modified lines. The global CI formatting
failure is a pre-existing baseline issue affecting 25 files across the
repository which is left unmodified to respect PR line-count limits.

Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant