Support `$.flags` context values in segment conditions
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start at the getFlags entry point and the project’s engine dependency declaration. Verify how segments are passed during identity-less evaluation, then run the existing test suite or relevant segment-condition tests; done means the engine version supports $.flags and $.environment conditions and getFlags resolves them without an identity.
Written by the indexing model from the issue text.
Description
Support $.flags.<feature name>.<enabled|value|variant> conditions.
Acceptance criteria
- The engine dependency is bumped to the version supporting
$.flagscontext values. getFlagspasses segments to the engine so identity-less evaluation resolves$.flagsand$.environmentconditions.
- Dominant language
- Python
- Stars
- 24
- Forks
- 12
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Flagsmith/flagsmith-python-client
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Dependency Dashboard Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Flagsmith/flagsmith-python-client#198 · 1 comment · 2 assignees ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in Flagsmith/flagsmith-python-client
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100