-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Fix allowedMaxRequests and allowedMaxCost values not showing in the settings UI #6925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your contribution! This is a clean and focused fix that correctly addresses the display issue.
The change properly converts values to using the nullish coalescing operator, which aligns with how the FormattedTextField component expects to handle empty values. The fix is minimal, targeted, and follows the existing patterns in the codebase.
LGTM! 🎯
| followupAutoApproveTimeoutMs={followupAutoApproveTimeoutMs} | ||
| allowedCommands={allowedCommands} | ||
| allowedMaxRequests={allowedMaxRequests ?? undefined} | ||
| allowedMaxCost={allowedMaxCost ?? undefined} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good fix! Using here ensures that values are properly converted to , which the FormattedTextField component expects for displaying empty fields. This is consistent with how the component's formatters are designed to work.
…ettings UI Fixes #1880 The kangaroo likes it: RooCodeInc/Roo-Code#6925
daniel-lxs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @chrarnoldus
|
Thank you! |
Kilo Code issue: Kilo-Org/kilocode#1880
Description
Relevant properties were not set on AutoApproveSettings, causes the value to be saved but not shown.
Test Procedure
Open settings, edit allowedMaxRequests and allowedMaxCost and verify the values stay on-screen when the inputs lose focus.
Get in Touch
Christiaan in shared Slack
Important
Fixes display issue for
allowedMaxRequestsandallowedMaxCostin settings UI by ensuring proper value assignment inSettingsView.tsx.allowedMaxRequestsandallowedMaxCostvalues were not displayed in the settings UI.undefinedif not provided, preventing display issues.SettingsViewinSettingsView.tsxto includeallowedMaxRequestsandallowedMaxCostwith fallback toundefined.This description was created by
for 9340758. You can customize this summary. It will automatically update as commits are pushed.