Skip to content
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

fix: update currentPage, pageSize values for portal #349

Merged
merged 3 commits into from
Nov 4, 2024

Conversation

kshitij-k-osmosys
Copy link
Contributor

@kshitij-k-osmosys kshitij-k-osmosys commented Oct 25, 2024

Portal PR Checklist

Pre-requisites

  • I have gone through the Contributing guidelines for Submitting a Pull Request (PR) and ensured that this is not a duplicate PR.
  • I have performed unit testing for the new feature added or updated to ensure the new features added are working as expected.
  • I have performed preliminary testing to ensure that any existing features are not impacted and any new features are working as expected as a whole.

PR Details

PR details have been updated as per the given format (see below)

  • PR title adheres to the format specified in guidelines (e.g., feat: add admin login page)
  • Description has been added
  • Related changes have been added (optional)
  • Screenshots have been added (optional, may include unit testing screenshots as well)
  • Pending actions have been added (optional)
  • Any other additional notes have been added (optional)

Additional Information

  • Appropriate label(s) have been added (ready for review should be added if the PR is ready to be reviewed)
  • Assignee(s) and reviewer(s) have been added (optional)

Note: Reviewer should ensure that the checklist and description have been populated and followed correctly, and the PR should be merged only after resolving all conversations and verifying that CI checks pass.


Description:

Update pageSize and currentPage values when calling notifications

Related changes:
NA

Screenshots:
NA

Pending actions:
NA

Additional notes:
NA

Summary by CodeRabbit

  • New Features

    • Enhanced pagination functionality for notifications, allowing users to navigate through notification pages more efficiently.
  • Bug Fixes

    • Improved error handling during notification fetching, providing users with clearer feedback when issues occur.

Copy link

coderabbitai bot commented Oct 25, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces enhancements to the NotificationsComponent class in notifications.component.ts, focusing on pagination for notifications. It adds properties for pageSize and currentPage to manage pagination state, updates the loading method to handle errors with RxJS, and ensures user feedback through the messageService. The existing filtering logic remains unchanged, but the integration of pagination modifies the control flow during notifications retrieval, along with adjustments to loading state management.

Changes

File Path Change Summary
apps/portal/src/app/views/notifications/notifications.component.ts - Added properties: pageSize and currentPage to manage pagination.
- Enhanced error handling in loadNotificationsLazy method using catchError from RxJS.
- Adjusted loading state management to ensure it reflects the fetching status.

Possibly related PRs

  • feat: add reload button for portal #346: Modifications to the notifications.component.html file, enhancing the user interface for notifications and potentially interacting with the pagination logic introduced.

Poem

🐇 In the land of notifications bright,
Pagination hops to new heights!
With pageSize and currentPage in play,
Errors caught, no dismay!
Loading states now dance with glee,
A happy rabbit, just wait and see! 🌟


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

@kshitij-k-osmosys kshitij-k-osmosys changed the title fix: update currentPage, pageSize & application event values fix: update currentPage, pageSize & application event values for portal Oct 25, 2024
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: 3

🧹 Outside diff range and nitpick comments (1)
apps/portal/src/app/views/notifications/notifications.component.ts (1)

279-284: Add documentation for pagination properties.

Consider adding TypeScript documentation comments to explain:

  • The purpose and constraints of pageSize and currentPage
  • The relationship between these properties and the LazyLoadEvent
  • Any validation rules or boundary conditions

Example documentation:

/** Number of items to display per page. Must be one of pageSizeOptions. */
pageSize = 10;

/** Current page number, 1-based indexing. Calculated from LazyLoadEvent. */
currentPage = 1;
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f26d27e and 72ae5d2.

📒 Files selected for processing (2)
  • apps/portal/src/app/views/notifications/notifications.component.html (1 hunks)
  • apps/portal/src/app/views/notifications/notifications.component.ts (1 hunks)
🔇 Additional comments (3)
apps/portal/src/app/views/notifications/notifications.component.html (2)

Line range hint 97-108: LGTM: Pagination configuration looks good.

The p-table configuration properly implements lazy loading with:

  • Dynamic page size using [rows]="pageSize"
  • Page size options through [rowsPerPageOptions]="pageSizeOptions"
  • Loading state indicator
  • Current page report

Line range hint 89-96: Verify pagination state management.

The reload button uses both currentPage and pageSize, while other actions reset to the first page. This might lead to inconsistent pagination states when reloading data.

Let's verify the pagination state management in the component:

apps/portal/src/app/views/notifications/notifications.component.ts (1)

279-284: Error handling improvements look good.

The addition of proper error handling with user feedback and loading state management is a good improvement.

@kshitij-k-osmosys kshitij-k-osmosys changed the title fix: update currentPage, pageSize & application event values for portal fix: update currentPage, pageSize values for portal Oct 27, 2024
@xixas xixas merged commit 0abe520 into main Nov 4, 2024
6 checks passed
@xixas xixas deleted the fix/pageSize-currentPage branch November 4, 2024 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants