[FIX]: Smooth scroll interruption resolved for USERS list.

[hustlernik]

What kind of change does this PR introduce?

This PR fixes bug related to interrupted scrolling of users list. Now the infinite scrolling of user list provides smoother experience.

Issue Number:

Fixes #2437

Did you add tests for your changes?

No

Snapshots/Videos:

Infinite-scroll-users-list.mp4

Does this PR introduce a breaking change?

No

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• New Features

  • Enhanced loading experience with a new loader for the users table.
  • Improved rendering logic for displaying users during data fetching.

• Bug Fixes

  • Streamlined the display of loading states for better clarity and performance.

• Refactor

  • Simplified the structure of the users table rendering for improved maintainability.

[coderabbitai]

Walkthrough

The Users component in src/screens/Users/Users.tsx has been updated to improve the infinite scrolling experience. A new constant tableLoaderRowLength is introduced to standardize the number of loader rows during data fetching. The loading logic for the InfiniteScroll component has been simplified, ensuring a more streamlined rendering process. The changes focus on enhancing the component's rendering clarity and loading state management.

Changes

File	Change Summary
src/screens/Users/Users.tsx	- Added tableLoaderRowLength constant set to 4 - Simplified InfiniteScroll loading logic - Improved table rendering structure

Assessment against linked issues

Objective	Addressed	Explanation
Smooth infinite scrolling [#2437]	✅

Possibly related PRs

• refactored CSS files in src/screens/Users #2600: Modifications to Users.tsx file, involving similar component structure and rendering logic changes

Suggested reviewers

• varshith257

Poem

🐰 Scrolling smooth, no more a jumpy ride
Users load with grace, pagination's pride
Four rows of loader, clean and neat
Infinite scroll now feels so sweet
CodeRabbit's magic makes users delight! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.

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.

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

src/screens/Users/Users.tsx (1)

73-73: Consider aligning tableLoaderRowLength with perPageResult

The loader displays 4 rows while actual data loads 12 rows per page. This mismatch could cause visual jumping when transitioning from loading to loaded state, potentially contributing to the scroll interruption issue.

-  const tableLoaderRowLength = 4;
+  const tableLoaderRowLength = perPageResult;

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 139e985 and 89af0fc.

📒 Files selected for processing (1)

• src/screens/Users/Users.tsx (2 hunks)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.35%. Comparing base (139e985) to head (89af0fc).
Report is 7 commits behind head on develop-postgres.

Additional details and impacted files

@@                 Coverage Diff                  @@
##           develop-postgres    #2726      +/-   ##
====================================================
+ Coverage             79.58%   86.35%   +6.77%     
====================================================
  Files                   295      312      +17     
  Lines                  7274     8135     +861     
  Branches               1592     1841     +249     
====================================================
+ Hits                   5789     7025    +1236     
+ Misses                 1222      933     -289     
+ Partials                263      177      -86     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.