feat(webui): Enforce 2-column layout for SQL input grid in guided Presto UI.#1638
Conversation
WalkthroughRefactored guided controls CSS grid from a responsive auto-fit layout (min 200px) to a fixed two-column grid (min 100px) and replaced multi-column span selectors with a single-column Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5–15 minutes
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (5)
🧰 Additional context used📓 Path-based instructions (1)**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}⚙️ CodeRabbit configuration file
Files:
🧠 Learnings (1)📓 Common learnings⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
🔇 Additional comments (6)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
i use the browser debugger tab to simulate various screen resolutions whose widths range from 1000px - 2560px. the layout is consistently 2-column which matches the purpose of the change.
for the title, how about:
feat(webui): Enforce a fixed 2-column layout for guided Presto search controls.
note the time range selector may overflow the window when the window width is less than 1000px, though i think that's unrelated to the current PR. we should submit an issue to track the fix if the problem is confirmed.
| gap: 5px; | ||
| } | ||
|
|
||
| .select { |
There was a problem hiding this comment.
kinda unrelated to the changes in this PR - would it be cleaner to just write
.select .from .where .order {
grid-column: span 1;
display: flex;
}to avoid repeating the style definitions? if in the future they will have different styles, we can always split the block?
There was a problem hiding this comment.
I changed to one class
|
@junhaoliao the overflow issue will be better after we merge the PR where the timekey selector is moved. There will be more space on the top row. |
|
@junhaoliao can you reapprove to due to merge conflicts |
Description
Previous grid in presto UI used auto-fit to dynamically position sql fields. Therefore on a larger screen, the layout could potentially be on one row. We determined this is undesirable, and now it is always on one row.
Checklist
breaking change.
Validation performed
always on 2 rows
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.