Restructure globalFilters state for per-table recent filters#3813
Restructure globalFilters state for per-table recent filters#3813
Conversation
Move recent filters tracking from the shared globalFilterOptions (unselectedDate on GlobalFilter) into a per-table recents map in state.tableFilters.globalFilters[tableId].recents. This ensures that unselecting a filter in one table does not show it as recent in another table. The middleware now sends both selected and recent filters to the backend, distinguished by the presence of unselectedDate. Signed-off-by: Florent MILLOT <75525996+flomillot@users.noreply.github.com>
…ved handling and sorting logic
…ter state handling
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
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 |
|
2 participants
PR Summary
This PR refactors the
globalFiltersstate structure to track recent filters per table. Previously, recent filters were shared across tables, resulting in unintended behavior when interacting with multiple tables. Recent filters are now stored instate.tableFilters.globalFilters[tableId].recents, ensuring they are managed distinctly per table.Additionally, the middleware has been updated to send both selected and recent filters to the backend, differentiating them using the
unselectedDatefield.