Users can then just pre-populate the default values (and so we can get rid of default struct tags and string parsing them as supported types) but OTOH, it does move the implicit default documentation away from where the field is defined and users could pre-populate parent commands too (although we don't support that -- we could technically support it though at the expense of some end user confusion?).
Users can then just pre-populate the default values (and so we can get rid of default struct tags and string parsing them as supported types) but OTOH, it does move the implicit default documentation away from where the field is defined and users could pre-populate parent commands too (although we don't support that -- we could technically support it though at the expense of some end user confusion?).