Summary
core/specs/probable.yaml declares id as type: integer on both Event and Market schemas. However, the live Probable API returns id as a string (e.g. "12345" not 12345). This type mismatch causes TypeScript type errors and may break ID comparison logic that expects numeric equality.
Impact
MEDIUM — ID comparison using === between a string ID from the API and an integer typed in code will always return false. Market/event lookups by ID will silently fail to match.
Details
- Field:
id on Event schema and Market schema in core/specs/probable.yaml
- Spec declares:
type: integer
- Live API returns: string (e.g.
"4201")
- Consequence: code that stores IDs as numbers and compares them to API responses will have comparison mismatches
Required Fix
Change id field type from integer to string in both the Event and Market schemas in core/specs/probable.yaml. Audit the Probable normalizer for any parseInt() or numeric ID handling that should be updated.
Summary
core/specs/probable.yamldeclaresidastype: integeron both Event and Market schemas. However, the live Probable API returnsidas a string (e.g."12345"not12345). This type mismatch causes TypeScript type errors and may break ID comparison logic that expects numeric equality.Impact
MEDIUM — ID comparison using
===between a string ID from the API and an integer typed in code will always returnfalse. Market/event lookups by ID will silently fail to match.Details
idon Event schema and Market schema incore/specs/probable.yamltype: integer"4201")Required Fix
Change
idfield type fromintegertostringin both the Event and Market schemas incore/specs/probable.yaml. Audit the Probable normalizer for anyparseInt()or numeric ID handling that should be updated.