Skip to content

Conversation

@bjp232004
Copy link
Contributor

@bjp232004 bjp232004 commented Aug 2, 2024

…or page refresh will be done

Summary by CodeRabbit

  • New Features

    • Introduced a new refreshHistogram property to improve histogram management within the logs component.
    • Enhanced the logs visualization to refresh the histogram in real-time when toggling log views.
  • Bug Fixes

    • Corrected conditions for refreshing the histogram to ensure data accuracy based on user interactions.

@bjp232004 bjp232004 linked an issue Aug 2, 2024 that may be closed by this pull request
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 2, 2024

Walkthrough

The recent changes enhance the management of histogram data within the logs component by introducing a refreshHistogram property to the state. This property determines when the histogram should be updated, shifting the control logic to focus on the current state of the component rather than just pagination. The updates improve user experience by ensuring that the displayed logs visualization remains accurate and responsive to query changes.

Changes

Files Change Summary
web/src/composables/useLogs.ts Added refreshHistogram to defaultObject, altering logic to manage histogram refresh based on this property. Updated handleRunQuery to set refreshHistogram to true when a new query is initiated.
web/src/plugins/logs/Index.vue Modified searchObj.meta to set refreshHistogram to true when logsVisualizeToggle is "logs", ensuring the histogram refreshes with active logs visualization.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Index.vue
    participant useLogs

    User->>Index.vue: Toggle logs visualization
    Index.vue->>useLogs: Set searchObj.meta.refreshHistogram = true
    useLogs->>useLogs: Check refreshHistogram
    useLogs-->>Index.vue: Refresh histogram data
Loading

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

@github-actions github-actions bot added ☢️ Bug Something isn't working 🧹 Updates labels Aug 2, 2024
@bjp232004 bjp232004 force-pushed the 4110-logs-page-pagination-back-to-1st-page branch from b1777a7 to 463a662 Compare August 2, 2024 10:55
Copy link
Contributor

@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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 20ac789 and 2f727c1.

Files selected for processing (2)
  • web/src/composables/useLogs.ts (4 hunks)
  • web/src/plugins/logs/Index.vue (2 hunks)
Additional comments not posted (5)
web/src/plugins/logs/Index.vue (2)

518-518: LGTM! Ensures histogram refresh when logs visualization is active.

This change correctly sets the refreshHistogram property to true to ensure the histogram is refreshed when the logs visualization is active.


556-556: LGTM! Ensures histogram refresh on component mount when logs visualization is active.

This change correctly sets the refreshHistogram property to true in the onBeforeMount lifecycle hook to ensure the histogram is refreshed when the component is mounted and the logs visualization is active.

web/src/composables/useLogs.ts (3)

100-100: Addition of refreshHistogram property looks good.

The refreshHistogram property is correctly added to the meta object within defaultObject and is set to false by default.


Line range hint 1674-1686:
LGTM! The logic for refreshing the histogram is correctly implemented.

The getQueryData function now includes checks for the refreshHistogram property, ensuring that the histogram is refreshed when necessary.


3487-3487: LGTM! The refreshHistogram property is correctly set to true.

The handleRunQuery function now sets refreshHistogram to true, ensuring that the histogram is refreshed when a new query is run.

@bjp232004 bjp232004 merged commit 4db3afd into main Aug 2, 2024
@bjp232004 bjp232004 deleted the 4110-logs-page-pagination-back-to-1st-page branch August 2, 2024 11:53
abvarun226 pushed a commit to abvarun226/openobserve that referenced this pull request Aug 8, 2024
openobserve#4112)

…or page refresh will be done

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
- Introduced a new `refreshHistogram` property to improve histogram
management within the logs component.
- Enhanced the logs visualization to refresh the histogram in real-time
when toggling log views.

- **Bug Fixes**
- Corrected conditions for refreshing the histogram to ensure data
accuracy based on user interactions.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@coderabbitai coderabbitai bot mentioned this pull request Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☢️ Bug Something isn't working 🧹 Updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logs page pagination back to 1st page

3 participants