HasOne relationship shows trashed resources

[Hannoma]

• Laravel Version: 8.83.9
• Nova Version: 4.2.5
• PHP Version: 8.1.3

Description:

In my user resource, there is a HasOne relationship to accesses. The accesses are using the soft-deleted trait. In Nova, the attached soft-deleted access is shown in the user detail page. In our case, this is not expected behavior and this behavior deviates from the HasOne relationship behavior of laravel/eloquent. Because in that case, soft-deleted models are not concerned. In addition, there is no method available like for the BelongsTo field to filter out trashed models.

Detailed steps to reproduce the issue on a fresh Nova installation:

Models/User.php

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

Nova/User.php

public function fields(NovaRequest $request): array
{
    // More fields here
    HasOne::make('Access')->exceptOnForms(),
}

Models/Access.php

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

Nova/Access.php

public function fields(NovaRequest $request): array
{
    // More fields here
    BelongsTo::make('User')
                ->exceptOnForms(),
}

[crynobone]

In our case, this is not expected behavior and this behavior deviates from the HasOne relationship behavior of laravel/eloquent.

Detail query is executed without global scope in order for Nova to still access soft deleted Access model.

Now, it seem that the relationship should have been User has one of many Access, where you can define it via:

// Models/User.php
public function profile()
{
    return $this->hasOne(Access::class)->ofMany()->latest()->withoutTrashed();
}

// Nova/User.php
public function fields(NovaRequest $request)
{
    return [
        HasOne::ofMany('Profile'),
    ];
}

[Hannoma]

It seems like that even this works:

// Models/User.php
public function access(): HasOne
{
    return $this->hasOne(Access::class)->ofMany();
}

[wajdijurry]

@Hannoma Short working answer. Thank you