mohammad-fouladgar / laravel-mobile-verification

src/Concerns/MustVerifyMobile.php

<?php

namespace Fouladgar\MobileVerification\Concerns;

use Fouladgar\MobileVerification\Notifications\VerifyMobile as VerifyMobileNotification;
use Illuminate\Config\Repository;

trait MustVerifyMobile
{
    /**
     * Determine if the user has verified their mobile number.
     */
    public function hasVerifiedMobile(): bool
    {
        return null !== $this->mobile_verified_at;
    }

    /**
     * Mark the given user's mobile as verified.
     */
    public function markMobileAsVerified(): bool
    {
        return $this->forceFill(['mobile_verified_at' => $this->freshTimestamp()])->save();

It seems like forceFill() must be provided by classes using this trait. How about adding it as abstract method to this trait?

It seems like freshTimestamp() must be provided by classes using this trait. How about adding it as abstract method to this trait?

    }

    /**
     * Send the mobile verification notification.
     */
    public function sendMobileVerifierNotification(string $token): void
    {
        $this->notify(new VerifyMobileNotification($token));

It seems like notify() must be provided by classes using this trait. How about adding it as abstract method to this trait?

    }

    /**
     * Get the mobile number that should be used for verification.
     */
    public function getMobileForVerification(): string
    {
        return $this->{$this->getMobileField()};
    }

    /**
     * Get the recipients of the given message.
     *
     * @return mixed
     */
    public function routeNotificationForVerificationMobile(): string
    {
        return $this->{$this->getMobileField()};
    }

    /**
     * @return Repository|mixed
     */
    private function getMobileField()
    {
        return config('mobile_verifier.mobile_column', 'mobile');
    }
}