8a7f9cb3709a9cee0295f1e52302f0306a954f8c
Drop the Number.isInteger normalization hack in useDeploymentPageState that mapped 1.0 → "1.0" but broke for values like 1.10 (which round-trip to 1.1). Instead, useFormDirty now parseFloats samplingRate on both sides before comparing, so "1", "1.0", and "1.00" all compare equal regardless of how the backend serializes the number. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
Observability server for Cameleer agents
Languages
Java
61.6%
TypeScript
30.2%
HTML
5.2%
CSS
2.9%