Skip to content

Commit d9f12ff

Browse files
committed
test(ofrep): follow the @numeric-coercion rename
The capability was renamed on the base branch, so this declaration named a symbol that no longer exists. OFREP keeps declaring it -- the provider satisfies the rule, for the same reason the Go OFREP provider does: OFREP is JSON, JSON has one number type, and the provider checks whether the round trip through an integer is lossy rather than assuming it is not. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
1 parent 3ff2f87 commit d9f12ff

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎providers/openfeature-provider-ofrep/tests/tck/test_ofrep_conformance.py‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@
4747
# ofrep/__init__.py:248 admits `(dict, list)` for FlagType.OBJECT -- so a JSON
4848
# object comes back as one rather than being rejected or flattened.
4949
#
50-
# STRICT_NUMERIC_TYPING
50+
# NUMERIC_COERCION
5151
# ofrep/__init__.py:250 maps FlagType.INTEGER to `int`, and the isinstance
5252
# check at ofrep/__init__.py:255 fails for the float 0.5, raising
5353
# TypeMismatchError. So float-flag's 0.5 is reported as a mismatch rather
@@ -119,7 +119,7 @@
119119
CAPABILITIES = frozenset(
120120
{
121121
Capability.OBJECT,
122-
Capability.STRICT_NUMERIC_TYPING,
122+
Capability.NUMERIC_COERCION,
123123
}
124124
)
125125

0 commit comments

Comments
 (0)