Skip to content

Conversation

@yehorkardash
Copy link

\b in regex doesn't work so well with Unicode characters. Replaced it with \p to be compatible with Unicode characters.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@gabor-openai
Copy link
Collaborator

Thank you for submitting this @yehorkardash, @steven10a and I are taking a look now!

Copy link
Collaborator

@steven10a steven10a left a comment

Choose a reason for hiding this comment

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

@yehorkardash Thank you for this PR! Could you do two things for us to get it ready to be merged? Otherwise I can implement them myself in a separate PR

  1. I believe this change would result in missing keywords that end or start with non-word characters. Can you test this with @foo matches inexample@foo.com and #foo in example#foo and add them to the unit tests?
  2. keywordsCheck is not async. Can you remove the async and await from the tests as commented

it('ignores text without the configured keywords', () => {
const result = keywordsCheck(
it('ignores text without the configured keywords', async () => {
const result = await keywordsCheck(
Copy link
Collaborator

Choose a reason for hiding this comment

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

keywordsCheck is not async can you remove async and await here and in all the tests added below.

@yehorkardash
Copy link
Author

Hey @gabor-openai, @steven10a, thanks for review and picking this up! I'll be able to get to update it only later this week, so I think you can close this PR and continue forward with your modified PR)

gabor-openai pushed a commit that referenced this pull request Nov 19, 2025
* Support Unicode characters in keywords check

Thank you @yehorkardash for finding this and submitting a fix in PR #41
@gabor-openai
Copy link
Collaborator

Thank you so much for this @yehorkardash! We implemented a similar fix in #46 based on your finding and PR.

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.

3 participants