fix: Clicking on pointer in data browser when using pagination does not reset to first page

[dblythy]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Closes: #2742

Approach

TODOs before merging

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

🚀 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.

[parseplatformorg]

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

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

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-63182

⌚ Updated Apr 26, 2025, 10:14 UTC

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

📄 View Application Logs etc.

What is Uffizzi? Learn more

[coderabbitai]

📝 Walkthrough

"""

Walkthrough

The change updates the handlePointerClick method in the Browser.react.js file to reset the pagination offset (skip) to zero whenever a pointer click navigates to a filtered browser view. This ensures that after clicking a pointer link, the pagination state is reset and the user is shown the first page of results. No other logic, control flow, or exported/public entity declarations are modified.

Changes

File(s)	Change Summary
src/dashboard/Data/Browser/Browser.react.js	Adds this.setState({ skip: 0 }) after navigation in handlePointerClick to reset pagination

Assessment against linked issues

Objective	Addressed	Explanation
Reset pagination params when clicking pointer links to filtered views (#2742)	✅
Ensure navigation to filtered object view does not retain previous page offset (#2742)	✅
"""

---

📜 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 4d52e80 and efcd757.

📒 Files selected for processing (1)

• src/dashboard/Data/Browser/Browser.react.js (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/dashboard/Data/Browser/Browser.react.js

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Docker linux/amd64

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.

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 docstrings to generate docstrings for this 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.

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-63244

⌚ Updated Apr 29, 2025, 01:21 UTC

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

📄 View Application Logs etc.

What is Uffizzi? Learn more

[parseplatformorg]

🎉 This change has been released in version 7.1.0-alpha.12