Proper schema syntax #51
Description
The use of the Lightbend/Typesafe Config library itself for purposes of parsing the input used to generate the wrapper has a number of limitations and counter-intuitive effects, in concrete when doing the automatic type detection from given values (NOTE: explicit types are not an issue). See for example #41, #50, #46.
This is not a fault of that library but rather a consequence of using it to infer the types. In particular, note that Lightbend/Typesafe Config:
- i) deals with concrete config input (as opposed to a schema as used in tscfg)
- ii) it complementarily offers multiple ways to get the value of the particular parameter, including
getInt,getDouble, etc., so, in other words, it defers to the user to decide how to access the value.
The proposal here is to define a proper syntax/language more appropriate for schema definition purposes and, along with that, implement/use a corresponding parsing mechanism. Although tscfg is not yet v1, perhaps consider forcing the new proper syntax as the default in some stable version, while also adding an option to indicate the particular input language.
Reactions/comments welcome.