open-feature / open-feature/java-sdk-contrib
[Flagsmith] Bump flagsmith-java-client from 7.4.3 to 8.x
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 81
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 6
Description
Provider
Flagsmith (dev.openfeature.contrib.providers:flagsmith, currently 0.0.13)
Problem
The Flagsmith provider pins com.flagsmith:flagsmith-java-client:7.4.3 (released Dec 2024). The latest client is 8.1.1. The 8.x line reworked how the evaluation context and identity are handled (8.0.0: "Context Values support" / "Actualise context schema", plus segment-override evaluation fixes such as Flagsmith/flagsmith-java-client#193 and Flagsmith/flagsmith-java-client#194).
Because the provider is stuck on 7.4.3, users on local evaluation hit a discrepancy: a segment rule defined against the identity key matches under remote evaluation but not under local evaluation. The same rule expressed against targetingKey matches in both modes, but targetingKey is a request-time context value and isn't persisted, so it isn't a substitute for matching a stored identity. The underlying client behaviour is addressed in 8.x.
Request
Bump the bundled flagsmith-java-client to the latest 8.x. Note 8.0.0 is a breaking release (new getEvaluationResult API and context schema changes), so this is not a drop-in version bump - the provider will need adapting to the new client API rather than a Renovate-style bump.
Links
- Client 8.0.0 release: https://github.com/Flagsmith/flagsmith-java-client/releases/tag/v8.0.0
- Latest client: https://github.com/Flagsmith/flagsmith-java-client/releases/tag/v8.1.1
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
Start with the Flagsmith provider dependency currently pinned to com.flagsmith:flagsmith-java-client:7.4.3 and read the 8.0.0 release notes, especially the getEvaluationResult API and context schema changes. Adapt the provider for the 8.1.1 client and verify that identity-based segment rules behave consistently in local and remote evaluation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100