Repository navigation
Conversation
|
| </SettingsRow> | ||
| <SettingsRow title="Theme" description="Choose how the dashboard looks." /> | ||
|
|
||
| <div class="grid grid-cols-3 gap-3"> |
There was a problem hiding this comment.
Theme cards crowd mobile
The fixed three-column grid leaves each card only about 88–106px wide on the mobile settings page, making the previews and labels cramped. Please make the grid responsive.
Prompt To Fix With AI
This is a comment left during a code review.
Path: dashboard/src/components/settings/forms/AppearanceForm.vue
Line: 41
Comment:
**Theme cards crowd mobile**
The fixed three-column grid leaves each card only about 88–106px wide on the mobile settings page, making the previews and labels cramped. Please make the grid responsive.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
@siduck See if Team can be a single setting item instead of Team and Manage. Two separate items does not make sense. Keep "System" instead of Automatic, and make it default in themes. Add a shortcut to open settings dialog - "Cmd + , " |
|
@siduck This diverges from espresso design system. Surfaces that are "floating" and closer to the user needs to be lighter than the background. |
I think we should re-consider for floating surfaces that have darker overlay tint behind them. because using elevation-1 instead of surface-base bg for dialog looks bright imo elevation-1 is around 16% lighter than bg-surface-base, ig makes sense for all floating items except dialog cuz it has overlaytint. bg-surface-base is around 53% lighter than the overlay tint and looks better for dialogs only |
refactor(ui): Add Consistent padding and gaps across all pages
| def leave_team(team: str) -> dict: | ||
| frappe.get_doc("Team", team).leave() |
There was a problem hiding this comment.
The new whitelisted endpoint passes the client-controlled team value into membership and document lookups without confirming it is a string. This violates the repository directive to explicitly validate input types at every whitelisted trust boundary and can allow complex values to reach Frappe’s ORM.
How this was verified: The endpoint forwards team into membership and document lookups without an explicit string check.
Context Used: Guidelines for reviewing Frappe Framework applications. (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: central/api/teams.py
Line: 240-241
Comment:
**Team input lacks validation**
The new whitelisted endpoint passes the client-controlled `team` value into membership and document lookups without confirming it is a string. This violates the repository directive to explicitly validate input types at every whitelisted trust boundary and can allow complex values to reach Frappe’s ORM.
**How this was verified:** The endpoint forwards `team` into membership and document lookups without an explicit string check.
**Context Used:** Guidelines for reviewing Frappe Framework applications. ([source](https://github.com/frappe/skills/blob/main/skills/quality-code-review/SKILL.md))
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Before
simplescreenrecorder-2026-09-06_18.23.49.mp4
After
simplescreenrecorder-2026-09-06_18.22.24.mp4