fix: missing type number for slider input right panel

[urmauur]

Describe Your Changes

Sorry my bad, the value should be Number instead string

Context:
There was an issue with a feature build that was behind the update, where the application loaded a model with some string parameters that should have been numbers.

To reproduce:
Build from any commits prior to this fix and behind the update.
Input a number into any number input box
Chat with model
See the error

Fixes Issues

• Closes #
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

[louis-jan]

Context:

There was an issue with a feature build that was behind the update, where the application loaded a model with some string parameters that should have been numbers.

Previous updates:

The number input component tries to cast the value to a string to fix the issue where users can just input ',' as a decimal separator.

That would address the input behavior and display to be aligned using the decimal point as a separator.

But the update led to a major issue where the persisted value was not cast to a number accordingly, which was rejected by the inference engine.

With the fix

These changes will keep the same display and input behavior but cast the value to a number before persisting.

To reproduce:

1. Build from any commits prior to this fix and behind the update.
2. Input a number into any number input box
3. Chat with model
4. See the error

[louis-jan]

LGTM

[louis-jan]

I will find a way to add tests for this case. For now please proceed until the next nightly build goes out. Which should affect a lot of users, but for now, only one case was able to be tested.

[github-actions]

Barecheck - Code coverage report

Total: 49.7%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered