[flagd/in-process] float flags with 0.0 value are parsed as ints

[toddbaert]

The flagd in-process provider should be able to resolve ints as floats, and vice-versa.

To fix:

• modify this area of the code to support conversion from int/float, float/int
• add relevant tests here
• un-comment float tests here

Background:

Originally posted by @toddbaert in #468 (comment)

[Kavindu-Dodan]

I summarised my findings here - https://github.com/open-feature/java-sdk-contrib/pull/468/files#r1344520202

IMO this can be safely fixed at the in-process provider end. A special handling for Double should fix this

[toddbaert]

IMO this can be safely fixed at the in-process provider end. A special handling for Double should fix this

I was thinking this too... in fact, to be consistent with RPC, I think we have to attempt conversion in both directions, int -> float and float -> int (RPC does this). Additionally, if we do this, we may need to specify how the float -> int conversion is done... I think Java and Go both round toward zero... I believe .NET does too. This might be worth specifying.

I will proceed with a fix as described above unless @Kavindu-Dodan or @beeme1mr disagrees.

[beeme1mr]

Yes, I agree that we should cast the values. This should be documented in the spec.

[DBlanchard88]

I think i understand how to do this. Ill take a shot at it.

[toddbaert]

I think i understand how to do this. Ill take a shot at it.

Alright, cool. Assigned.