Use ONE form for 2 resources

Hi @lorenzoberti

Why not just use one form, pass the form's data to your controller and update both models from the update method: https://laravel.com/docs/5.8/eloquent-relationships#inserting-and-updating-related-models

Because I would like use a Default Laravel Nova behavior (resources and Models) for save, update, delete. if I have to write/override these I would buy an pure html/css theme.

Ah, sorry, missed the NOVA part.

I don't know Nova at all really, but my eyes widened in surprise when I saw this and I had to go and look at the docs. There's full support for all relationship types in Laravel so the front end you are developing should be written as suggested by @mstrauss

From the docs:

In addition to the variety of fields we've already discussed, Nova has full support for all of Laravel's relationships. Once you add relationship fields to your Nova resources, you'll start to experience the full power of the Nova dashboard, as the resource detail screen will allow you to quickly view and search a resource's related models

Is this not what you want?

Hello thankyou, Yes Nova has full support for Relationship but... If I use a Hasone relationship for create a Form, with 2 Model connected, I should firstly , create a model and then add data for second model, so 2 form.

Immagine now, that you would like create a User form where You have to set Username, password, email, name, lastname, phone and others data relative to USERDETAIL model. You should create user (with username password email) save, and then go on the other page with the form with the user details.

And now I've found this issue that confirm my doubt:

https://github.com/laravel/nova-issues/issues/777

I see, that's interesting and yes, I agree, it should probably be changed for this use case.

Thanks for coming back and updating this thread with this answer will probably help me and others in the future :)

Has there been any more work on this? I'm also new to Nova and have not explored this in detail, however, this is a very common use case. E-Commerce is another example where, when creating a main product, you might want to create variations on the same page.

I have do it at route level.

First you need to identify the route your resource is using, for example, to override the create method from the resource Post, the route will be something like (you can use artisan route:list):

/nova-api/posts.

Then in your web.php file override the route, but here is the important part, you need to add the Nova middleware to add the security rules from Nova. You can group all the routes that you need to override:

// Override Nova Routes  
Route::middleware(config('nova.middleware'))->group(function () {  
 Route::post('/nova-api/posts', 'PostController@myCustomFunctionForCreateNovaResource');  
});