You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that I am running the latest version of the COMET-SDK
I have searched open and closed issues to ensure it has not already been reported
Description
At the moment numeric (Double) values cannot be entered with group seperators, for example 123,123.10.
This is caused by the fact that the Double.TryParse call that is used in ValueSetConverter.ToValueSetString, uses NumberStyles.Float.
It should probably use NumberStyles.Any, so all possible numeric values can be converted to a ValueSet string.
Please notice that for example a Boolean Parametertype value entered by the user as a value of "0", or "1" leads to a positive Boolean.TryParse result, but also as a Double.TryParse result.
Order of individual code lines is important to stay backwards compatible and also collaboration with the ValueSetConverter.ToValueSetObject should be an area of interest, as boolean values are converted to real Boolean values there.
Seems like a boolean parametertype Value that is used in ValueSetConverter.ToValueSetString already doesn't work at the moment.
There might be other types that have similar problems.
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
At the moment numeric (Double) values cannot be entered with group seperators, for example 123,123.10.
This is caused by the fact that the Double.TryParse call that is used in
ValueSetConverter.ToValueSetString
, uses NumberStyles.Float.It should probably use NumberStyles.Any, so all possible numeric values can be converted to a ValueSet string.
Please notice that for example a Boolean Parametertype value entered by the user as a value of "0", or "1" leads to a positive Boolean.TryParse result, but also as a Double.TryParse result.
Order of individual code lines is important to stay backwards compatible and also collaboration with the ValueSetConverter.ToValueSetObject should be an area of interest, as boolean values are converted to real Boolean values there.
Seems like a boolean parametertype Value that is used in ValueSetConverter.ToValueSetString already doesn't work at the moment.
There might be other types that have similar problems.
The text was updated successfully, but these errors were encountered: