Bug fix/Execution History Pagination Defect fixed 41037, 41046 and 41047

[GokulBothe99]

Thank you for your contribution.
Before submitting this PR, please make sure:

• PR description and commit message should describe the changes done in this PR
• Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
• Latest Code from master or specific release branch is merged to your branch
• No unwanted\commented\junk code is included
• No new warning upon build solution
• Code Summary\Comments are added to my code which explains what my code is doing
• Existing unit test cases are passed
• New Unit tests are added for your development
• Sanity Tests are successfully executed for New and Existing Functionality
• Verify that changes are compatible with all relevant browsers and platforms.
• After creating pull request there should not be any conflicts
• Resolve all Codacy comments
• Builds and checks are passed before PR is sent for review
• Resolve code review comments
• Update the Help Library document to match any feature changes

Summary by CodeRabbit

• New Features

  • Enhanced execution history page with improved data handling and visibility controls based on execution logger settings.
  • Introduced asynchronous methods for loading remote data and execution history, improving UI responsiveness.

• Bug Fixes

  • Improved error handling for GraphQL data loading, providing better feedback for connection issues.

• Refactor

  • Updated method naming for clarity, focusing on reloading execution history data.

• UI Improvements

  • Enhanced pagination logic to accurately reflect data state, improving user experience.

[coderabbitai]

Walkthrough

The changes involve enhancements to the RunSetsExecutionsHistoryPage class and a modification in the NewRunSetPage.xaml.cs file. Key updates include the introduction of new properties and methods for managing execution history data, refined event handling for UI interactions, improved error handling in GraphQL data loading, and updated pagination logic to reflect the state of displayed data.

Changes

Files	Change Summary
Ginger/Ginger/Run/RunSetsExecutionsHistoryPage.xaml.cs, Ginger/Ginger/RunSetPageLib/NewRunSetPage.xaml.cs	Introduced new properties/methods for execution history management, improved UI responsiveness, refined error handling, updated method calls for reloading data.

Poem

In the meadow where data flows,
A rabbit hops where execution grows.
With tweaks and turns, the code does shine,
As history’s tales align just fine.
Hooray for changes, let’s celebrate,
With binkies of joy, it’s truly great! 🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e7d1ad4 and 84bfdfe.

Files selected for processing (2)

• Ginger/Ginger/Run/RunSetsExecutionsHistoryPage.xaml.cs (18 hunks)
• Ginger/Ginger/RunSetPageLib/NewRunSetPage.xaml.cs (1 hunks)

Additional comments not posted (11)

Ginger/Ginger/Run/RunSetsExecutionsHistoryPage.xaml.cs (10)

43-43: LGTM!

The new imports are necessary for the added functionality.

The code changes are approved.

---

59-64: LGTM!

The class declaration remains unchanged.

The code changes are approved.

---

77-78: LGTM!

The new boolean flags isGraphQlClinetConfigure and waitForPageCreation are well-named and seem to manage the state of the GraphQL client and the loading process.

The code changes are approved.

---

116-133: LGTM!

The constructor modifications are logical and improve the initialization process.

The code changes are approved.

---

135-147: LGTM!

The new method OnExecutionLoggerConfigPublishLogToCentralDB_Changed effectively handles changes to the PublishLogToCentralDB property and updates the visibility of execution history controls.

The code changes are approved.

---

149-167: LGTM!

The new method SetExectionHistoryVisibility correctly sets the visibility of execution history controls based on the PublishLogToCentralDB property.

The code changes are approved.

---

169-201: LGTM!

The new method AssignGraphQLObjectEndPoint correctly assigns the GraphQL endpoint for the execution report client and handles connection errors.

The code changes are approved.

---

205-215: LGTM!

The new method LoadExectionHistory correctly checks the centralized execution logger configuration and sets the appropriate radio button, then loads the executions history data.

The code changes are approved.

---

221-227: LGTM!

The new method LoadRemoteData correctly loads remote execution history data asynchronously.

The code changes are approved.

---

232-250: LGTM!

The new event handler RemoteRadioButton_Selected correctly shows the button panel, assigns the GraphQL endpoint, and loads the executions history data using GraphQL.

The code changes are approved.

Ginger/Ginger/RunSetPageLib/NewRunSetPage.xaml.cs (1)

1757-1757: LGTM!

The function is correctly updated to call ReloadExecutionHistoryData instead of ReloadData.

The code changes are approved.