Incorrect `reason` used for environment default flags

Open
#341 1 comment 0 reactions 1 assignee View on GitHub

@bakirFS is already working on this.

Since Sep 9, 2026.

Assessment

This issue has not been assessed yet.

Description

Currently the engine emits DEFAULT whenever the evaluation result is the environment default flag.

This should be:

  1. STATIC if there are no targeting rules configured for the feature
  2. DEFAULT if there are targeting rules configured, but the evaluation doesn't match them

i.e. if there are segment overrides for a feature, but they don't match the identity we are evaluating for, then return DEFAULT. If there are no segment overrides, return STATIC.

See Resolution Reason.

Acceptance Criteria:

  • Change implemented in this repository and tested
  • New version of engine released
  • New engine version integrated into Flagsmith/flagsmith, Flagsmith/edge-api, Flagsmith/flagsmith-python-client, Flagsmith/edge-proxy
  • Update reason logic in Flagsmith/flagsmith-go-client
Dominant language
Python
Stars
10
Forks
5
Avg merge
4d 8m
Merged PRs (30d)
3

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-engine

All issues in Flagsmith/flagsmith-engine

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.