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
Size-in-bytes conversion should be explicitly (not optionally) specified by user using size | <size>. Unless this is explicitly specified, tscfg should assume it is a string by default; no implicit conversion should be done. (This is also the default behaviour of Typesafe Config.)
Example:
In each of the following cases, tscfg currently generates a variable memory of type Long, with value 53687091200.
memory: 50G
memory: "50G"
To be consistent with the default behavior of Typesafe Config, which doesn't make assumptions about types unless explicitly requested (e.g., using methods such as getBytes, getInt, etc), tscfg should instead generate a variable memory of type String, with value "50G". This should be the default behavior, unless the user explicitly requests a size-in-bytes comparison as follows:
Size-in-bytes conversion should be explicitly (not optionally) specified by user using
size | <size>
. Unless this is explicitly specified, tscfg should assume it is a string by default; no implicit conversion should be done. (This is also the default behaviour of Typesafe Config.)Example:
In each of the following cases, tscfg currently generates a variable
memory
of typeLong
, with value53687091200
.To be consistent with the default behavior of Typesafe Config, which doesn't make assumptions about types unless explicitly requested (e.g., using methods such as
getBytes
,getInt
, etc), tscfg should instead generate a variablememory
of typeString
, with value "50G". This should be the default behavior, unless the user explicitly requests a size-in-bytes comparison as follows:(This has been discussed at length in #41).
The text was updated successfully, but these errors were encountered: