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
Right now, if there is a more complex config, for example a file containing some JSON configuration, the caller has to first load the config, then parse it:
What is the feature you are proposing to solve the problem?
I'd like to have an API that combines the loading of the config with its parsing. Something like:
// config module// for simplicity's sake, otherwise it could be a dual APIexportdeclareconstschema: <constCextendsstring,A>(name: C,schema: Schema.Schema<A,string>,)=>Config.Config<A>
What is the problem this feature would solve?
Right now, if there is a more complex config, for example a file containing some JSON configuration, the caller has to first load the config, then parse it:
What is the feature you are proposing to solve the problem?
I'd like to have an API that combines the loading of the config with its parsing. Something like:
and then at the call site:
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: