[12.x] Introducing Rules\Password::appliedRules Method

[devajmeireles]

We know that the most interesting way to standardize password validation is through Rules/Password for backend.

However, when it comes to, for example, displaying the same validation rules from the backend on the frontend, we have a block due to the lack of a method that makes it possible to obtain the rules applied via AppServiceProvider.

This PR introduces the Rules\Password::appliedRules method that makes it possible to have an array containing the validation rules and their respective usage statuses, which allow us to access what was defined in the backend to display the rules that are actually accepted in a given password field.

Example:

class AppServiceProvider extends ServiceProvider
{
    // ...

    public function boot(): void
    {
        Password::defaults(function () {
            return Password::min(8)
                ->mixedCase()
                ->numbers();
        });
    }
}

use Illuminate\Contracts\View\View;
use Illuminate\Validation\Rules\Password;
use Livewire\Component;

class Profile extends Component
{
    // ...

    public function render(): View
    {
        return view('livewire.profile', [
            'appliedRules' => Password::default()->appliedRules(),
        ]);
    }

    public function save(): void
    {
        // ...
    }
}

<div>
    <form wire:submit="save">
        <div>
            <x-input label="Password" />

            <span>{{ __('The password must be at least :min characters long.', ['min' => $appliedRules['min']]) }}</span>

            @if ($appliedRules['mixedCase'] === true)
                <span>{{ __('The password must contain at least one uppercase and one lowercase letter.') }}</span>
            @endif

            @if ($appliedRules['numbers'] === true)
                <span>{{ __('The password must contain at least one number.') }}</span>
            @endif
        </div>
        <x-button type="submit">
            Save
        </x-button>
    </form>
</div>

[utsavsomaiya]

        @if ($appliedRules['mixedCase'] === true)
            <span>{{ __('The password must contain at least one uppercase and one lowercase letter.') }}</span>
        @endif

        @if ($appliedRules['numbers'] === true)
            <span>{{ __('The password must contain at least one number.') }}</span>
        @endif

May be this would be always based on js framework like alpine?

[devajmeireles]

        @if ($appliedRules['mixedCase'] === true)
            <span>{{ __('The password must contain at least one uppercase and one lowercase letter.') }}</span>
        @endif

        @if ($appliedRules['numbers'] === true)
            <span>{{ __('The password must contain at least one number.') }}</span>
        @endif

May be this would be always based on js framework like alpine?

I believe that regardless of the type of frontend, appliedRules will be useful.

Two examples:

1. Imagine a NuxtJS-based frontend consumes your Laravel API. We can use Password::appliedRules to pass the expected password format to NuxtJS so that NuxtJS prints it gracefully.
2. FluxUI may have a form-specific password component that displays the expected password format at any time, so again, Password::appliedRules will be useful to match the password format between the frontend and the backend.

[utsavsomaiya]

Yeah but it will remove or changing the colors based on the input! May be yeah you're right idk!