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

PCH Sidebar: Show detailed error messages in Snackbar Notices #2579

Merged

Conversation

acicovic
Copy link
Collaborator

@acicovic acicovic commented Jun 26, 2024

Description

With this PR, we start displaying detailed error messages in our Snackbar Notices in the Title Suggestions and Smart Linking features.

Motivation and context

  • When errors would occur in Title Suggestions and Smart Linking, we were showing a generic "There was an error" Snackbar Notice. While we were displaying the detailed error message in the PCH Sidebar, the Snackbar Notice proved to be unhelpful or even confusing to users, with the error within the Sidebar remaining unnoticed in some cases. This change should neutralize this problem.
  • Fixes PCH: Consider forwarding main UI errors to Snackbar Notices #2424. This was a known issue, and I stumbled upon it while working on other things. While fixing it, I decided to extract it to its own PR for easier review and separation of concerns.

How has this been tested?

Manual testing.

Summary by CodeRabbit

  • New Features

    • Added a new error type UnknownError to improve error handling.
    • Dynamic error messages are now displayed based on the actual error encountered.
  • Improvements

    • Reordered import statements for better code organization.

@acicovic acicovic added this to the 3.16.0 milestone Jun 26, 2024
@acicovic acicovic self-assigned this Jun 26, 2024
Copy link
Contributor

coderabbitai bot commented Jun 26, 2024

Walkthrough

Walkthrough

The changes implement improved error handling by introducing a new UnknownError code to the ContentHelperErrorCode enum. This aids in more comprehensive error handling across different components. Additionally, the modifications include updating how errors are handled within the SmartLinkingPanel and using dynamic error messages instead of static ones in the TitleSuggestions component.

Changes

Files Change Summary
src/content-helper/common/content-helper-error.tsx Introduced UnknownError to ContentHelperErrorCode and included it in the ContentHelperError class.
src/.../editor-sidebar/smart-linking/component.tsx Imported ContentHelperError and ContentHelperErrorCode, reordered imports, and modified error handling logic within SmartLinkingPanel.
src/.../editor-sidebar/title-suggestions/component.tsx Replaced a static error message with a dynamic one retrieved from error.message.

Sequence Diagram(s)

Not applicable due to the straightforward nature of the changes focusing on error handling and error message updates.

Assessment against linked issues

Objective Addressed Explanation
Forwarding main UI errors to Snackbar Notices (#2424) The summary provided doesn't explicitly mention forwarding errors to Snackbar Notices. Further review of the code is necessary.

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

@acicovic acicovic marked this pull request as ready for review June 28, 2024 05:59
@acicovic acicovic requested a review from a team as a code owner June 28, 2024 05:59
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: 1

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 58a1d92 and f40cd5f.

Files ignored due to path filters (6)
  • build/content-helper/dashboard-widget.asset.php is excluded by !build/**
  • build/content-helper/dashboard-widget.js is excluded by !build/**
  • build/content-helper/editor-sidebar.asset.php is excluded by !build/**
  • build/content-helper/editor-sidebar.js is excluded by !build/**
  • build/content-helper/excerpt-generator.asset.php is excluded by !build/**
  • build/content-helper/excerpt-generator.js is excluded by !build/**
Files selected for processing (3)
  • src/content-helper/common/content-helper-error.tsx (2 hunks)
  • src/content-helper/editor-sidebar/smart-linking/component.tsx (5 hunks)
  • src/content-helper/editor-sidebar/title-suggestions/component.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
  • src/content-helper/editor-sidebar/title-suggestions/component.tsx
Additional context used
Path-based instructions (2)
src/content-helper/common/content-helper-error.tsx (1)

Pattern **/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:

  • Review the code to ensure it is well-structured and adheres to best practices.
  • Verify compliance with WordPress coding standards.
  • Ensure the code is well-documented.
  • Check for security vulnerabilities and confirm the code is secure.
  • Optimize the code for performance, removing any unnecessary elements.
  • Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
  • Ensure each line comment concludes with a period.
  • Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
  • Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."
src/content-helper/editor-sidebar/smart-linking/component.tsx (1)

Pattern **/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:

  • Review the code to ensure it is well-structured and adheres to best practices.
  • Verify compliance with WordPress coding standards.
  • Ensure the code is well-documented.
  • Check for security vulnerabilities and confirm the code is secure.
  • Optimize the code for performance, removing any unnecessary elements.
  • Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
  • Ensure each line comment concludes with a period.
  • Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
  • Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."
Additional comments not posted (4)
src/content-helper/common/content-helper-error.tsx (2)

33-33: Addition of UnknownError to ContentHelperErrorCode enum.

The addition of UnknownError as a new error code seems appropriate for handling unspecified errors that may not fit other predefined categories.


71-71: Inclusion of UnknownError in noRetryFetchErrors array.

Adding UnknownError to the list of errors that should not trigger a retry is a prudent decision. It prevents unnecessary retry attempts in cases where the error nature is unclear.

src/content-helper/editor-sidebar/smart-linking/component.tsx (2)

18-18: Import addition for error handling.

The import of ContentHelperError and ContentHelperErrorCode is necessary for the updated error handling logic in SmartLinkingPanel. This is a well-structured change to support the enhanced functionality.


473-477: Enhanced error handling in SmartLinkingPanel.

The creation of ContentHelperError based on dynamic error details (e.message and e.code) is a significant improvement. It ensures that errors are handled more gracefully and informatively, aligning with the PR's objectives.

Copy link
Contributor

@vaurdan vaurdan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for working on this! I left a comment regarding the console.error removal, but other than that, I consider this PR approved.

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.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f40cd5f and 75ed7e8.

Files ignored due to path filters (2)
  • build/content-helper/editor-sidebar.asset.php is excluded by !build/**
  • build/content-helper/editor-sidebar.js is excluded by !build/**
Files selected for processing (1)
  • src/content-helper/editor-sidebar/smart-linking/component.tsx (4 hunks)
Files skipped from review as they are similar to previous changes (1)
  • src/content-helper/editor-sidebar/smart-linking/component.tsx

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.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 75ed7e8 and 9ca9925.

Files ignored due to path filters (6)
  • build/content-helper/dashboard-widget.asset.php is excluded by !build/**
  • build/content-helper/dashboard-widget.js is excluded by !build/**
  • build/content-helper/editor-sidebar.asset.php is excluded by !build/**
  • build/content-helper/editor-sidebar.js is excluded by !build/**
  • build/content-helper/excerpt-generator.asset.php is excluded by !build/**
  • build/content-helper/excerpt-generator.js is excluded by !build/**
Files selected for processing (2)
  • src/content-helper/common/content-helper-error.tsx (2 hunks)
  • src/content-helper/editor-sidebar/title-suggestions/component.tsx (1 hunks)
Files skipped from review as they are similar to previous changes (2)
  • src/content-helper/common/content-helper-error.tsx
  • src/content-helper/editor-sidebar/title-suggestions/component.tsx

@acicovic acicovic merged commit 198a494 into develop Jul 4, 2024
37 checks passed
@acicovic acicovic deleted the update/pch-sidebar-show-detailed-error-in-snackbar-notices branch July 4, 2024 11:45
@acicovic acicovic changed the title PCH Sidebar: Show detailed error messages in snackbar Notices PCH Sidebar: Show detailed error messages in Snackbar Notices Jul 8, 2024
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.

PCH: Consider forwarding main UI errors to Snackbar Notices
2 participants