Feat:(issue_1960) make defaults validation optional

[dearchap]

What type of PR is this?

(REQUIRED)

• documentation
• feature

What this PR does / why we need it:

(REQUIRED)

The feature allows default validation to be optional.

Which issue(s) this PR fixes:

(REQUIRED)

Fixes #1960

Special notes for your reviewer:

(fill-in or delete this section)

Testing

(fill-in or delete this section)

make test

Release Notes

(REQUIRED)

Defaults validation is optional(false). Validation of defaults, values from env can be enabled by setting ValidateDefaults to true

[dearchap]

@urfave/cli I'm wondering if we need to validate values from ValueSources(like Env, File etc) but not the default that the user sets explicitly via Value . Thoughts ?

[Juneezee]

I'm wondering if we need to validate values from ValueSources(like Env, File etc) but not the default that the user sets explicitly via Value . Thoughts ?

I believe this would be a valuable feature. We could potentially create a Validator struct to accommodate future extensions, such as:

type Validator[T any] struct {
	ValidateFunc     func(T) error `json:"-"`
	ValidateDefaults bool          `json:"validateDefaults"`
	ValidateSources  bool          `json:"validateSources"`
}