Support `$.flags` context values in segment conditions

Open
#224 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
api, backend

Research direction

Start by locating the engine condition evaluation and the SDK getFlags path, then inspect engine-test-data for the flag dependency cases. Implement support for $.flags conditions and segment passing while preserving per-evaluation isolation and avoiding cost when unused. Done means the bumped engine-test-data cases pass and identity-less evaluations resolve $.flags and $.environment conditions.

Written by the indexing model from the issue text.

Description

Support $.flags.<feature name>.<enabled|value|variant> conditions.

Acceptance criteria

Engine:

  • engine-test-data is bumped to the tag containing the flag dependency cases, and they pass.
  • An environment with no $.flags conditions gains no per-evaluation cost.
  • Resolved flags are scoped to a single evaluation, never shared between concurrent evaluations.

SDK:

  • getFlags passes segments to the engine so identity-less evaluation resolves $.flags and $.environment conditions.
Dominant language
Java
Stars
28
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-java-client

All issues in Flagsmith/flagsmith-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.