Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support `$.flags` context values in segment conditions

Open
#292 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
nodejs, typescript
Domain
api, backend

Research direction

Start by locating getFlags and the engine integration, then inspect the engine-test-data dependency and its flag dependency cases. Verify that $.flags conditions work for identity-less evaluations, environments without such conditions avoid per-evaluation cost, and resolved flags remain isolated across concurrent evaluations.

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
TypeScript
Stars
30
Forks
27
Avg merge
20h 52m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

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-nodejs-client

All issues in Flagsmith/flagsmith-nodejs-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.