PostHog / PostHog/posthog-ruby
Add feature flag evaluation context parity
Open
Nobody has claimed this yet.
enhancement
feature/flags
- Dominant language
- Ruby
- Stars
- 36
- Forks
- 34
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 18
Description
Summary
Add missing feature flag evaluation context parity to the Ruby SDK.
Specs
sdk-specs/openspec/specs/get-feature-flag/spec.mdsdk-specs/openspec/specs/is-feature-enabled/spec.mdsdk-specs/openspec/specs/local-feature-flag-evaluator/spec.md
Current evidence
The SDK audit found that flag APIs lack device_id; legacy/bulk APIs also lack some newer context options.
Expected behavior
- Allow passing
device_idthrough relevant feature flag evaluation APIs. - Use
device_idin local/remote evaluation where required by the flag definition/evaluation context. - Bring legacy and bulk flag APIs closer to the canonical server-side context options where applicable.
- Add tests for remote request body propagation and local evaluation bucketing/context behavior.
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.
Research direction
Read sdk-specs/openspec/specs/get-feature-flag/spec.md, is-feature-enabled/spec.md, and local-feature-flag-evaluator/spec.md first, then trace the corresponding Ruby SDK APIs. Done means device_id and applicable context options reach remote requests and local evaluation, with tests covering request-body propagation, bucketing, and context behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100