Skip to content

fix: Data browser not scrolling to top when changing filter while cell selected #2821

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 25, 2025

Conversation

mtrezza
Copy link
Member

@mtrezza mtrezza commented May 25, 2025

New Pull Request Checklist

Issue Description

Data browser not scrolling to top when changing filter while cell selected

Approach

When filter is applied or removed then scroll to top.

Summary by CodeRabbit

  • Refactor
    • Improved user experience when changing filters or classes by automatically scrolling to the top of the page and clearing any cell selection or editing state.
    • Pagination now reliably resets to the first page when filters or classes are changed.

Copy link

parse-github-assistant bot commented May 25, 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 25, 2025

📝 Walkthrough

Walkthrough

The code refactors pagination reset logic in the Browser component by introducing a new resetPage() method. This method centralizes actions such as clearing selection, canceling editing, scrolling to the top, and resetting pagination. Multiple callback handlers are updated to use this new method instead of repeating similar code.

Changes

File(s) Change Summary
src/dashboard/Data/Browser/Browser.react.js Refactored repeated pagination reset logic into a new resetPage() method and updated handlers.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Browser
    participant DataBrowserRef

    User->>Browser: Trigger filterClicked/removeFilter/classClicked
    Browser->>Browser: resetPage()
    Browser->>DataBrowserRef: clearSelection()
    Browser->>DataBrowserRef: cancelEditing()
    Browser->>Window: scrollTo(top, smooth)
    Browser->>Browser: setState({ skip: 0 })
Loading

Possibly related PRs

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm warn config production Use --omit=dev instead.
npm error code ERR_SSL_WRONG_VERSION_NUMBER
npm error errno ERR_SSL_WRONG_VERSION_NUMBER
npm error request to https://10.0.0.28:4873/npm/-/npm-10.9.2.tgz failed, reason: C05C6ED20A7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
npm error
npm error A complete log of this run can be found in: /.npm/_logs/2025-05-25T11_44_06_059Z-debug-0.log


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.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/dashboard/Data/Browser/Browser.react.js (1)

1922-1940: Good implementation that addresses the stated issue, but consider adding null checking.

The resetPage() method effectively centralizes the pagination reset logic and addresses the scrolling issue mentioned in the PR objectives. The implementation correctly:

  • Clears cell selection and cancels editing
  • Scrolls to the top with smooth behavior
  • Resets pagination to the first page

Consider adding null checking for better defensive programming:

  resetPage() {
    // Unselect any currently selected cell and cancel editing action
-   this.dataBrowserRef.current.setCurrent(null);
-   this.dataBrowserRef.current.setEditing(false);
+   if (this.dataBrowserRef.current) {
+     this.dataBrowserRef.current.setCurrent(null);
+     this.dataBrowserRef.current.setEditing(false);
+   }

    // Scroll to top
    window.scrollTo({
      top: 0,
      behavior: 'smooth'
    });

    // Reset pagination to page 1
    this.setState({
      skip: 0,
    });
  }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 17923d4 and 6107122.

📒 Files selected for processing (1)
  • 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 (3)
src/dashboard/Data/Browser/Browser.react.js (3)

1906-1909: LGTM! Good refactoring to centralize pagination reset logic.

The replacement of direct setState({ skip: 0 }) with this.resetPage() is a good improvement that consolidates the reset behavior and addresses the scrolling issue mentioned in the PR objectives.


1910-1913: LGTM! Consistent with the refactoring pattern.

Good use of the centralized resetPage() method for the removeFilter callback to ensure consistent reset behavior.


1914-1916: LGTM! Completes the consistent refactoring pattern.

The use of resetPage() in the classClicked callback maintains consistency with the other navigation actions.

Copy link

uffizzi-cloud bot commented May 25, 2025

Uffizzi Ephemeral Environment deployment-63885

⌚ Updated May 25, 2025, 11:47 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/2821

📄 View Application Logs etc.

What is Uffizzi? Learn more

@mtrezza mtrezza merged commit c2527dc into parse-community:alpha May 25, 2025
10 of 11 checks passed
parseplatformorg pushed a commit that referenced this pull request May 25, 2025
# [7.2.0-alpha.7](7.2.0-alpha.6...7.2.0-alpha.7) (2025-05-25)

### Bug Fixes

* Data browser not scrolling to top when changing filter while cell selected ([#2821](#2821)) ([c2527dc](c2527dc))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.2.0-alpha.7

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label May 25, 2025
@mtrezza mtrezza deleted the fix/scroll-to-top branch May 25, 2025 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released-alpha Released as alpha version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants