How would you use Laravel Data package to validate requests for setting manipulation?

[serious-angel]

Dear Developers,

Thank you for the marvel!

---

For example, we have the following setting:

namespace App\Settings\General;

use App\Enums\Color;
use Spatie\LaravelSettings\Settings;

class ColorSettings extends Settings
{
    public bool $enabled = false;

    public Color $name = Color::White;

    /** @var \App\Enums\ColorShade[] */
    public array $shades = [];

    public static function group(): string
    {
        return 'general_color';
    }
}

We have the package Laravel Data already installed, since it was mentioned in the scaffolded configuration file for Laravel Settings:

laravel-settings/config/settings.php

Line 78 in fd3db34

Spatie\LaravelData\Data::class => Spatie\LaravelSettings\SettingsCasts\DataCast::class,

Would you create a definite class like the following?:

namespace App\Data;

use App\Enums\Color;
use App\Enums\ColorShade;
use Illuminate\Validation\Rule;
use Spatie\LaravelData\Attributes\MergeValidationRules;
use Spatie\LaravelData\Data;

#[MergeValidationRules]
final class ColorSettingsData extends Data
{
    public function __construct(
        public bool $enabled,
        public Color $name,
        public array $shades,
    ) {}

    public static function rules(): array
    {
        return [
            'shades.*' => [
                'distinct',
                Rule::enum(ColorShade::class),
            ],
        ];
    }

    public static function messages(): array
    {
        return [
            'shades.*' => 'Invalid Color shades',
        ];
    }
}

The above separate class seems interesting, but perhaps, I currently don't see a more proper way to use the setting in proper request for API with the package Laravel Data features (e.g. custom rule messages, TypeScript), and would I appreciate a hint on how to prepare a request class for the setting.

---

Best and kind regards