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

Add comma to boundary for domains #1116

Merged
merged 1 commit into from
Oct 28, 2024
Merged

Conversation

nmalzieu
Copy link
Contributor

@nmalzieu nmalzieu commented Oct 28, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced error handling for peer identity resolution, providing clearer feedback when a peer's identity is not found.
  • Bug Fixes

    • Improved regular expression patterns for better boundary detection, including commas as valid boundary characters.

These updates aim to enhance user experience by ensuring more informative alerts and refining text processing capabilities.

@nmalzieu nmalzieu requested a review from a team as a code owner October 28, 2024 10:43
Copy link
Contributor

coderabbitai bot commented Oct 28, 2024

Walkthrough

The changes in this pull request involve modifications to the openMainConversationWithPeer function in utils/conversation.ts, specifically enhancing error handling when a peer's identity is not found. The error message now incorporates the variable peerToCreateConvoWith, improving user feedback. Additionally, two regular expression constants in utils/regex.ts have been updated to include a comma in their patterns, affecting boundary detection in various contexts. The core logic of both functions remains unchanged.

Changes

File Change Summary
utils/conversation.ts Modified openMainConversationWithPeer to enhance error handling by including peerToCreateConvoWith in the error message. No changes to conversationLastMessagePreview.
utils/regex.ts Updated BOUNDARY_START_LOOKBEHIND and BOUNDARY_END_LOOKAHEAD regex patterns to include a comma as a valid boundary character. Structure and logic remain unchanged.

Possibly related PRs

  • Fabri QA for frames & deeplinks #1098: The changes in the Conversation component regarding the initialization logic for conversations and the handling of topics may relate to the modifications in the openMainConversationWithPeer function's error handling, as both involve user feedback and conversation management.

Poem

🐇 In the garden of code, where errors once lay,
A message now blooms, brightening the way.
With commas in regex, boundaries align,
Conversations flourish, all thanks to design!
So hop with delight, as we fix and refine,
In the world of our code, everything's fine! 🌼


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.

Copy link
Contributor

Performance Comparison Report

  • Current: 61961a3 - 2024-10-28 10:47:30Z
  • Baseline: main (1ff4410) - 2024-10-28 10:46:52Z

Significant Changes To Duration

There are no entries

Meaningless Changes To Duration

Show entries
Name Type Duration Count
Avatar Image 10 runs render 1.0 ms → 1.2 ms (+0.2 ms, +20.0%) 🔴 1 → 1
Avatar Image 50 runs render 1.1 ms → 1.0 ms (-0.1 ms, -8.9%) 1 → 1
Empty Avatar 10 runs render 1.1 ms → 0.9 ms (-0.2 ms, -18.2%) 🟢 1 → 1
Empty Avatar 50 runs render 0.7 ms → 0.7 ms (-0.1 ms, -8.1%) 1 → 1
Show details
Name Type Duration Count
Avatar Image 10 runs render Baseline
Mean: 1.0 ms
Stdev: 0.5 ms (47.1%)
Runs: 1 2 1 1 1 0 1 1 1 1
Warmup runs: 2

Current
Mean: 1.2 ms
Stdev: 0.4 ms (35.1%)
Runs: 1 2 1 1 1 1 1 2 1 1
Warmup runs: 2
Baseline
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1
Render issues:

Current
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1
Render issues:
Avatar Image 50 runs render Baseline
Mean: 1.1 ms
Stdev: 0.3 ms (29.3%)
Runs: 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 2 2 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 2 1 1 1 1
Warmup runs: 1

Current
Mean: 1.0 ms
Stdev: 0.1 ms (13.9%)
Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1
Warmup runs: 1
Baseline
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Render issues:

Current
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Render issues:
Empty Avatar 10 runs render Baseline
Mean: 1.1 ms
Stdev: 0.3 ms (28.7%)
Runs: 1 2 1 1 1 1 1 1 1 1
Warmup runs: 69

Current
Mean: 0.9 ms
Stdev: 0.3 ms (35.1%)
Runs: 1 1 1 1 1 0 1 1 1 1
Warmup runs: 8
Baseline
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1
Render issues:

Current
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1
Render issues:
Empty Avatar 50 runs render Baseline
Mean: 0.7 ms
Stdev: 0.4 ms (59.9%)
Runs: 1 1 1 1 1 1 0 0 0 0 1 1 1 0 1 1 1 1 1 0 1 1 0 1 1 1 1 1 1 0 0 1 1 1 1 1 0 1 1 0 1 1 1 1 0 1 1 1 0 1
Warmup runs: 1

Current
Mean: 0.7 ms
Stdev: 0.5 ms (69.3%)
Runs: 1 1 1 1 1 1 1 1 0 1 1 0 1 0 1 1 0 1 1 1 1 1 0 1 1 1 1 1 1 0 1 0 0 1 0 1 0 0 0 1 0 1 0 1 1 1 1 0 0 1
Warmup runs: 1
Baseline
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Render issues:

Current
Mean: 1
Stdev: 0 (0.0%)
Runs: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Render issues:

Render Count Changes

There are no entries

Render Issues

There are no entries

Added Scenarios

There are no entries

Removed Scenarios

There are no entries

Generated by 🚫 dangerJS against 4a42425

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

🧹 Outside diff range and nitpick comments (2)
utils/regex.ts (2)

1-1: Update the comment to include the comma boundary.

The regex pattern has been correctly updated to include a comma as a valid boundary character, but the inline comment should be updated to reflect this change.

-const BOUNDARY_START_LOOKBEHIND = /(\s|\(|"|'|,)/.source; // Either a space or a (, or a " or a '
+const BOUNDARY_START_LOOKBEHIND = /(\s|\(|"|'|,)/.source; // Either a space, (, ", ', or ,

3-3: Update the comment to include the comma boundary.

The regex pattern has been correctly updated to include a comma as a valid boundary character, but the inline comment should be updated to reflect this change.

-const BOUNDARY_END_LOOKAHEAD = /(\s|\)|$|\.|!|\?|\r\n|\r|\n|"|'|,)/.source; // Either a space, the end of the text, or a ), a ., a !, a ?, a line break, or a " or a '
+const BOUNDARY_END_LOOKAHEAD = /(\s|\)|$|\.|!|\?|\r\n|\r|\n|"|'|,)/.source; // Either a space, end of text, ), ., !, ?, line break, ", ', or ,
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 1ff4410 and 4a42425.

📒 Files selected for processing (2)
  • utils/conversation.ts (1 hunks)
  • utils/regex.ts (1 hunks)
🔇 Additional comments (3)
utils/regex.ts (1)

1-3: Verify the impact on domain matching behavior.

The addition of commas as valid boundaries appears correct for supporting comma-separated lists of domains. Let's verify this doesn't introduce any regressions.

utils/conversation.ts (2)

274-274: LGTM: Error message translation looks good!

The error message translation is properly implemented, maintaining consistency with the error handling flow and correctly including the peer's identity in the message.


274-274: Request for additional files to review

The PR title mentions adding comma to boundary for domains, but the regex changes in utils/regex.ts are not included in the files for review. Could you please include utils/regex.ts in the review to ensure the boundary changes are properly implemented?

✅ Verification successful

Regex changes for domain boundaries are properly implemented

The changes in utils/regex.ts show that comma (,) is correctly included in both boundary definitions:

  • BOUNDARY_START_LOOKBEHIND includes comma in its pattern: (\s|\(|"|'|,)
  • BOUNDARY_END_LOOKAHEAD includes comma in its pattern: (\s|\)|$|\.|!|\?|\r\n|\r|\n|"|'|,)

These changes ensure proper handling of comma-separated domain names in the text.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the regex changes in utils/regex.ts
# Test: Look for BOUNDARY related constants
rg -l 'BOUNDARY_(START_LOOKBEHIND|END_LOOKAHEAD)'

Length of output: 66


Script:

#!/bin/bash
# Let's check the actual content of utils/regex.ts to see the regex changes
cat utils/regex.ts

Length of output: 1917

@nmalzieu nmalzieu merged commit 6825113 into main Oct 28, 2024
6 checks passed
@nmalzieu nmalzieu deleted the noe/username-boundary-comma branch October 28, 2024 14:05
technoplato pushed a commit that referenced this pull request Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants