Bogdan Drutu
Bogdan Drutu
> There are a few fields in confighttp structs that use e.g. a pointer to int instead of an int. This is an unusual pattern in configuration from components, so...
This reminds me of something. We should add a `NewDefaultFoo` for all configs, so that we can easily add new fields and set the right default value. So we can...
> Not all strings are valid component.Types, but all strings are valid configopaque.Strings, so I don't think we get anything out of making this a struct. Indeed, but I am...
@mx-psi then why do we test it with `yaml/v3`? What is special about it?
> But also, it be a big breaking change - at this point the use is quite widespread - the benefits may not outweigh the costs. We can do it...
@mx-psi should we add also an rc phase for this?
> However, the parameter component.Type is not used. Should we remove it? Please
@jpkrohling removed the ready-to-use since I believe this does not work for multiple calls to get settings, because of that I think is better to design a different API.
Can you give me until mid July before marking any config stable? I want to also discuss somewhere and document things like: * Adding new validation rules means breaking change?...