Default values (again!!)

[Zirbo]

Hallo,
I know this has been mentioned plenty of times (#462, #165 (comment) and so on) and that you can implement UnmarshalYAML to set your own defaults.
Buuuuuut if you have multiple types of configs, and in each of them just a single field needs a default, implementing UnmarshalYAML in each of them makes your code quite bloated. It really seems complexity that could be hidden in the library itself.
Is something like

type Config struct {
    A string  `string_name, omitempty, default="abc"`
    B int       `int_name, omitempty, default=10`
    C bool    `bool_name, omitempty, default=true`
}

in the roadmap? Or is there some deeper reason (I mean in the code) for this missing feature so it will never be implemented?

[rew1nter]

This would be so nice

[fishjam]

I want this feature too.
but seems this project is no longer maintained, there are already 100+ PR pending :(

[MeNsaaH]

I believe this fork has been created by k8s maintainers and would can serve for now: kubernetes-sigs/yaml#76

[romshark]

Or is there some deeper reason (I mean in the code) for this missing feature so it will never be implemented?

The reason is: it's already possible without struct tags.
https://go.dev/play/p/SPwo265oeO2

[Zirbo]

Or is there some deeper reason (I mean in the code) for this missing feature so it will never be implemented?

The reason is: it's already possible without struct tags. https://go.dev/play/p/SPwo265oeO2

You, my good sir, are amazing. This is not what I wanted, but it's almost as good.

If I ever meet you in person, you will drink as much beer as you want without ever having to touch your wallet.