Skip to content

Conversation

zdyj3170101136
Copy link

@zdyj3170101136 zdyj3170101136 commented Oct 14, 2025

first, it fixed #1202, escape space correctly.

second, it could recognized space without escape.

so the old lucene search:
"failed\\ to\\ do\\ something" could be converted to "failed to do something"

Copy link

changeset-bot bot commented Oct 14, 2025

⚠️ No Changeset found

Latest commit: 3decdbf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 14, 2025

@zdyj3170101136 is attempting to deploy a commit to the HyperDX Team on Vercel.

A member of the Team first needs to authorize it.

@zdyj3170101136
Copy link
Author

@MikeShi42

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.

Lucene search syntax doesn't escape space properly

1 participant