-
Notifications
You must be signed in to change notification settings - Fork 620
[TOOL-2800] Insight Playground: Combine all filter query params in a group #5807
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
[TOOL-2800] Insight Playground: Combine all filter query params in a group #5807
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5807 +/- ##
=======================================
Coverage 53.34% 53.34%
=======================================
Files 1101 1101
Lines 59124 59124
Branches 4824 4824
=======================================
Hits 31541 31541
Misses 26864 26864
Partials 719 719
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|
Merge activity
|
6f1a918 to
ed047fd
Compare
…group (#5807) ## Problem solved Short description of the bug fixed or feature added <!-- start pr-codex --> --- ## PR-Codex overview This PR enhances the `RequestConfigSection` component by restructuring how parameters are categorized into `pathVariables`, `queryParams`, and `filterQueryParams`. It introduces a new `ParameterSection` for `filterQueryParams` and improves the styling of parameter sections. ### Detailed summary - Replaced direct filtering of `props.parameters` with a `useMemo` hook for better performance. - Added categorization of parameters into `pathVariables`, `queryParams`, and `filterQueryParams`. - Introduced a new `ParameterSection` for rendering `filterQueryParams`. - Updated the `ParameterSection` to accept a `className` prop for styling. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
b5ff31e to
dc088f2
Compare
…group (#5807) ## Problem solved Short description of the bug fixed or feature added <!-- start pr-codex --> --- ## PR-Codex overview This PR enhances the `RequestConfigSection` component by improving the handling of parameters. It introduces a new categorization for query parameters, separating them into general query parameters and filter query parameters, and updates the rendering logic accordingly. ### Detailed summary - Refactored parameter handling in `RequestConfigSection` using `useMemo`. - Introduced `filterQueryParams` to categorize parameters starting with "filter_". - Updated rendering to conditionally display `ParameterSection` for `filterQueryParams`. - Added `className` prop to `ParameterSection` for styling flexibility. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->
ed047fd to
58b75d1
Compare
dc088f2 to
fd4664a
Compare

Problem solved
Short description of the bug fixed or feature added
PR-Codex overview
This PR enhances the
RequestConfigSectioncomponent by restructuring how parameters are categorized, introducing a new grouping for filter query parameters, and improving the rendering of parameter sections.Detailed summary
pathandqueryparameters with a singleuseMemohook.filterQueryParamsthat captures parameters starting with "filter_".ParameterSectionforfilterQueryParams.ParameterSectionto accept an optionalclassNameprop.