Skip to content

feat: Add test case for a flag dependency on a feature with a non-ASCII name - #66

Merged
emyller merged 1 commit into
mainfrom
feat/unicode-escaped-flag-dependency
Nov 4, 2026
Merged

emyller merged 1 commit into
mainfrom
feat/unicode-escaped-flag-dependency

Conversation

@khvn26

@khvn26 khvn26 commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Adds a test case ensuring a dependency on a feature with a non-ASCII name, written as the API writes it, is resolved.

How did you test this code?

Each implementation was run against its pinned test data with this case added:

Implementation Result
flagsmith-engine main ✅
flagsmith-go-client main ✅
flagsmith-java-client main ✅
flagsmith-rust-flag-engine main ✅
flagsmith-dotnet-client main ✅
Flagsmith/flagsmith-elixir-client#67 ✅
flagsmith-nodejs-client main ❌
flagsmith-ruby-client main ❌
Flagsmith/flagsmith-php-client#150 ❌

The three failures are identical: dependent keeps its default with reason DEFAULT, and no segment matches.

Contributes to SDK-6

Review effort: 1/5

…II name

Flagsmith writes a dependency's condition as
`$.flags[<json.dumps(name)>].enabled`, which escapes non-ASCII characters,
so a dependency on `été` reads `$.flags["\u00e9t\u00e9"].enabled`. Engines
that look the escaped name up verbatim never match the dependency's segment.
@khvn26
khvn26 requested a review from a team as a code owner November 4, 2026 19:45
@khvn26
khvn26 requested review from emyller and removed request for a team November 4, 2026 19:45
@linear-code

linear-code Bot commented Nov 4, 2026

Copy link
Copy Markdown

SDK-6

@emyller
emyller merged commit da82e78 into main Nov 4, 2026
2 checks passed
@emyller
emyller deleted the feat/unicode-escaped-flag-dependency branch November 4, 2026 20:03
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