open-feature / open-feature/java-sdk-contrib
feat!: adopt numeric coercion contract
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 81
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 6
Description
Adopts the numeric coercion ADR in the flagd provider.
- implement lossless numeric coercion in the in-process resolver (per-language flagd-core)
- for
ResolveAll/AnyFlag.double_value, apply the same lossless check client-side so bulk eval matches individualResolve*behavior - bump
flagd-testbedsubmodule; adopt@numeric-coercion-v2and drop old@numeric-coercionexclusions/scenarios - coordinated release with other providers
- breaking; call out in release notes
Covers both providers/flagd and the bundled providers/flagd-core (Java).
Parent: https://github.com/open-feature/flagd/issues/1995
Depends on
Blocked until the following land first:
- open-feature/flagd#1996 (flagd + flagd-core implementation)
- open-feature/flagd-testbed#379 (
@numeric-coercion-v2scenarios and new testbed release)
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 the numeric coercion ADR and inspect providers/flagd plus the bundled providers/flagd-core Java implementation. Wait for open-feature/flagd#1996 and flagd-testbed#379, then update the testbed submodule and adopt the v2 scenarios while removing the old exclusions. Done means both individual and bulk resolution follow the lossless contract and the breaking release is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, release, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100