It is not possible to enter `1.0` as a value

[mrexodia]

Inspector Version

• 0.17.2

Describe the bug
It is not possible to enter 1.0 as a parameter value.

To Reproduce
Steps to reproduce the behavior:

1. Type 1. in the parameter field
2. Press 0

Expected behavior
See 1.0 in the parameter field, it reverts back to 1 instead.

• OS: Windows
• Browser Chrome

Additional context
I need to receive a JSON-RPC call containing 1.0, because just 1 will be converted to an integer in my language (Python):

>>> type(json.loads("1"))
<class 'int'>
>>> type(json.loads("1.0"))
<class 'float'>

Version Consideration

Inspector V2 is under development to address architectural and UX improvements. See CONTRIBUTING.md for information about V2 development.

[olaservo]

I think this is more of a limitation of JavaScript and JSON than an issue with the Inspector, so one way we might handle this is by saving and serializing the float values as strings, which could then parsed in the server as floats. We could also try to add a raw json mode to these fields. Not sure yet what would be the best way to handle this.

[majiayu000]

Hi, I've been looking into this and traced the root cause.

Proposed approach: Extend DynamicJsonForm's number handling (building on PR #1127's raw text preservation pattern) to preserve trailing zeros when serializing values for JSON-RPC. Option A: On blur, keep the raw text representation and use it directly when building JSON payloads (bypassing JS number normalization). Option B: Add a raw JSON toggle to parameter fields as the maintainer suggested. Option A is simpler and more targeted. Add a test verifying 1.0 is sent as 1.0 (not 1) in the JSON-RPC call.

I'll open a draft PR shortly. Happy to adjust based on your preference.