[linear-code]

Local evaluation in the Rust SDK accepted a regex match anywhere in a trait value, so prod put nonproduction in a segment. The documented behaviour is that a match must start at the beginning of the value but doesn't need to cover all of it. This applies to every alternative, so prod|dev matches development but not nondev. The SDK picks this up once it's released and the SDK's engine dependency is bumped.

Changes

• Regex segment conditions match only from the start of the trait value, with no full-match requirement
• The same rule applies to the legacy segment condition API
• Invalid patterns still never match. The pattern isn't rewritten, so something like a)(b can't turn into a valid regex.
• Added regression cases for prefix, mid-string, alternation, end-anchored and case-sensitive matching
• Rust SDK uses an engine release that includes this fix

Closes https://linear.app/flagsmith/issue/SDK-29/standardise-regex-matching-in-the-rust-server-side-sdk

Review effort: 1/5

[linear-code]

SDK-29

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 91fc3d78-be16-4851-9830-aa310a82c548

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[linear-code]

@coderabbitai review