[ENH] Implement literal expression for regex

[Sicheng-Pan]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • N/A
• New functionality
  • Implement custom internal representations for regular expression. They will be used with full text search index to filter documents.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[Sicheng-Pan]

• [CLN] Rename $matches to $regex #4506
• [BUG] Fix blockfile range scan #4467
• [ENH] Wireup regex in filter operator #4452
• [ENH] Implement literal provider #4430
• [ENH] Implement literal expression for regex #4421 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[propel-code-bot]

Implementation of Literal Expression for Regular Expressions

This PR adds custom internal representations for regular expressions in the Rust codebase to be used with full text search for document filtering. The implementation includes a ChromaHir enum that creates a simplified representation of regex patterns, along with validation logic to ensure patterns are specific enough for efficient filtering.

Key Changes:
• Added ChromaHir struct to represent regex patterns in a custom, simplified format
• Implemented LiteralExpr to extract literal expressions from regex patterns
• Added validation to ensure regex patterns contain at least one 3-character literal string
• Integrated regex validation in the document filtering system

Affected Areas:
• rust/types/src/regex/ (new module with 3 new files)
• rust/types/src/where_parsing.rs
• rust/types/src/lib.rs

This summary was automatically generated by @propel-code-bot

[Sicheng-Pan]

Merge activity

• May 9, 12:59 PM EDT: A user started a stack merge that includes this pull request via Graphite.
• May 9, 12:59 PM EDT: @Sicheng-Pan merged this pull request with Graphite.