How to Show User Fields in one to one Model in Laravel Nova?

[mohammad6006]

I create a project with Laravel nova I create Doctor model and resource User and Doctor has one to one relation

User Model:

public function doctor(): HasOne
{
    return $this->hasOne(Doctor::class);
}

Doctor Model:

public function user(): BelongsTo
{
    return $this->belongsTo(User::class);
}

Now I want to fill user fields from Doctor resource:

Doctor resource:

public function fields(NovaRequest $request)
{
    return [
        ID::make()->sortable(),
        
        Text::make('User Name', 'user.name')
            ->sortable()
            ->rules('required', 'max:255'),

        Text::make('User Email', 'user.email')
            ->sortable()
            ->rules('required', 'email', 'max:254')
            ->creationRules('unique:users,email')
            ->updateRules('unique:users,email,{{resourceId}}'),

        Password::make('User Password', 'user.password')
            ->onlyOnForms()
            ->creationRules('required', Rules\Password::defaults())
            ->updateRules('nullable', Rules\Password::defaults()),

        Text::make('First Name', 'first_name')
            ->sortable()
            ->rules('required', 'max:255'),

        Text::make('Last Name', 'last_name')
            ->sortable()
            ->rules('required', 'max:255'),

In this Doctor fields:

first_name and last_name are in doctors table but user name, email and password are in users table

when I create new doctor it show

The User Name field is required.

[milewski]

You could use a BelongsTo field with the ->showCreateRelationButton() on forms, and outside forms you can use HasOne, something like this:

public function fields(NovaRequest $request): array
{
    return [
        ID::make()->sortable(),

        Text::make('First Name', 'first_name')
            ->sortable()
            ->rules('required', 'max:255'),

        Text::make('Last Name', 'last_name')
            ->sortable()
            ->rules('required', 'max:255'),

        BelongsTo::make('Doctor', 'doctor', Doctor::class)
            ->onlyOnForms()
            ->showCreateRelationButton(),

        HasOne::make('Doctor', 'doctor', Doctor::class)
            ->exceptOnForms(),
    ];
}

Even though the relationship is not a HasOne, the HasOne field would work perfectly fine on details, for index you could implement fieldsForIndex() and use the dot notation picking you have currently