Skip to content

fix: Selecting a saved filter in data browser may highlight a different filter #2783

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

Merged
merged 1 commit into from
May 3, 2025

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented May 3, 2025

New Pull Request Checklist

Issue Description

Selecting a saved filter in data browser may visually highlight a different filter.

Approach

Move sorting of filter alphabetically to earlier stage.

Summary by CodeRabbit

  • Refactor
    • Updated filter lists to display in their original order in one area and in alphabetical order in another, ensuring a more consistent and intuitive user experience across different parts of the interface.

Copy link

parse-github-assistant bot commented May 3, 2025

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Copy link

coderabbitai bot commented May 3, 2025

📝 Walkthrough

Walkthrough

The changes adjust how filter arrays are ordered in two components. In the CategoryList component, the explicit sorting of filters by their name property before rendering was removed, so filters now appear in their original order. Conversely, in the Browser component within the dashboard, filters are now sorted alphabetically by their name property before being assigned to each row. No changes were made to the declarations or signatures of exported or public entities in either file.

Changes

File(s) Change Summary
src/components/CategoryList/CategoryList.react.js Removed sorting of filters by name before rendering; filters are now rendered in original order.
src/dashboard/Data/Browser/Browser.react.js Added sorting of filters by name before assigning to each row in the sidebar rendering logic.

Sequence Diagram(s)

sequenceDiagram
    participant BrowserComponent
    participant FilterArray

    BrowserComponent->>FilterArray: Retrieve filters for each row
    BrowserComponent->>FilterArray: Sort filters by name (localeCompare)
    BrowserComponent->>BrowserComponent: Assign sorted filters to row
Loading
sequenceDiagram
    participant CategoryListComponent
    participant FilterArray

    CategoryListComponent->>FilterArray: Retrieve filters from c.filters
    CategoryListComponent->>CategoryListComponent: Render filters in original order
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a2f421 and 005b95d.

📒 Files selected for processing (2)
  • src/components/CategoryList/CategoryList.react.js (1 hunks)
  • src/dashboard/Data/Browser/Browser.react.js (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Docker linux/amd64
🔇 Additional comments (2)
src/dashboard/Data/Browser/Browser.react.js (1)

1876-1877: Good fix for the filter selection highlight issue.

This change correctly implements alphabetical sorting of filters at the data preparation stage, which ensures consistent ordering before filters are passed to the CategoryList component. This aligns with the PR objective to fix the visual highlighting discrepancy when selecting saved filters.

The localeCompare() method is an appropriate choice for alphabetical string sorting.

src/components/CategoryList/CategoryList.react.js (1)

140-140: Good removal of redundant sorting.

This change correctly removes the sorting of filters at the rendering stage, as this is now being handled earlier in the Browser.react.js file. By removing the duplicate sorting here, the code:

  1. Avoids unnecessary processing
  2. Ensures the component respects the order of filters as provided
  3. Fixes the visual highlighting inconsistency mentioned in the PR objectives

This change works in tandem with the modification in Browser.react.js to ensure filters are sorted exactly once before being displayed.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@parseplatformorg
Copy link
Contributor

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

@mtrezza mtrezza changed the title fix: Selecting a saved filter in data browser may visually highlight a different filter fix: Selecting a saved filter in data browser may highlight a different filter May 3, 2025
@mtrezza mtrezza merged commit 4c6e853 into parse-community:alpha May 3, 2025
10 of 11 checks passed
@mtrezza mtrezza deleted the fix/filter-highlight branch May 3, 2025 10:49
parseplatformorg pushed a commit that referenced this pull request May 3, 2025
## [7.1.1-alpha.3](7.1.1-alpha.2...7.1.1-alpha.3) (2025-05-03)

### Bug Fixes

* Selecting a saved filter in data browser may highlight a different filter ([#2783](#2783)) ([4c6e853](4c6e853))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.1.1-alpha.3

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label May 3, 2025
parseplatformorg pushed a commit that referenced this pull request Jun 1, 2025
# [7.2.0](7.1.0...7.2.0) (2025-06-01)

### Bug Fixes

* Data browser not scrolling to top when changing filter while cell selected ([#2821](#2821)) ([c2527dc](c2527dc))
* Data browser table shows loading indicator when info panel is loading ([#2782](#2782)) ([da57e5e](da57e5e))
* Improperly aligned unfolding sub-items in context menu in data browser ([#2726](#2726)) ([3fed292](3fed292))
* Notifications fade out erratically when executing a script on large number of rows ([#2822](#2822)) ([3891381](3891381))
* Pagination does not reset to page 1 when clicking on class or filter ([#2798](#2798)) ([29d1447](29d1447))
* Saving new filter in data browser overwrites filters added in other dashboard instances ([#2769](#2769)) ([46bc154](46bc154))
* Selecting a saved filter in data browser may highlight a different filter ([#2783](#2783)) ([4c6e853](4c6e853))

### Features

* Add confirmation dialog before saving a Cloud Config parameter that has been modified since editing it ([#2770](#2770)) ([adb9b5c](adb9b5c))
* Add custom CSS styling for info panel items ([#2788](#2788)) ([f031e5d](f031e5d))
* Add relative date filter in data browser for date constraints relative to when the query is run ([#2736](#2736)) ([d9dfd69](d9dfd69))
* Add script execution on parallel batches with option `script.executionBatchSize` ([#2828](#2828)) ([cee8b8d](cee8b8d))
* Keyboard Enter key can be used to select item in data browser filter dialog field dropdown ([#2771](#2771)) ([dc14710](dc14710))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.2.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Jun 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants