Replacing ozzo validation.Required

github.com/go-ozzo/ozzo-validation/v4 changed Required semantics in v4.4.0. Zero-valued structs now count as empty, which means code that previously treated decoded struct values as present can start failing after the upgrade.

Upstream references:

What changed

Before ozzo v4.4.0, validation.Required treated most zero-valued structs as present. After v4.4.0, zero-valued structs are considered empty.

This affects patterns like:

type Flags struct {
    Enabled bool
}

type Config struct {
    Flags Flags
}

func (c Config) Validate() error {
    return validation.ValidateStruct(&c,
        validation.Field(&c.Flags, validation.Required),
    )
}

With newer ozzo versions, Config{Flags: Flags{}} now fails validation.Required.

Replacement in golang-utils

Use github.com/ARM-software/golang-utils/utils/validation.IsRequired instead.

IsRequired is an alias of IsRequiredLegacy and preserves the older ozzo behavior that many configuration-style validations relied on:

Migration

Replace this:

import validation "github.com/go-ozzo/ozzo-validation/v4"

func (c Config) Validate() error {
    return validation.ValidateStruct(&c,
        validation.Field(&c.Flags, validation.Required),
    )
}

With this:

import (
    ozzovalidation "github.com/go-ozzo/ozzo-validation/v4"
    utilsvalidation "github.com/ARM-software/golang-utils/utils/validation"
)

func (c Config) Validate() error {
    return ozzovalidation.ValidateStruct(&c,
        ozzovalidation.Field(&c.Flags, utilsvalidation.IsRequired),
    )
}

If your file already imports golang-utils validation helpers, the change is often just:

validation.Field(&cfg.Flags, validationutils.IsRequired)

instead of:

validation.Field(&cfg.Flags, validation.Required)

When to keep ozzo validation.Required

Keep ozzo's built-in validation.Required when you explicitly want zero values to be rejected, such as:

Rule choice summary