Organising controllers and models for creating records that can be related to two other models

Or a SchoolContactsController and StudentContactsController? is what i would opt for..in which case yur functions in those file will be simply index() create().. etc instead of

something complicated if you decide to go for ContactsController..

Thanks. I guess from those controllers I would then call a method on each of the School/Student models called addContact?

no you will have a create function in each controller and pass in school id which you can use eloquent to get the model and then save the contacts details..

@jammy-git You have two “nested” resources: a school contact and a student contact. Therefore, I’d create two separate controllers (SchoolContactController and StudentContactController) but look at opportunities to DRY the code.

With relationships set up properly, adding a contact should look like $school->contacts()->create($request->all()). Similarly, $student->contact()->create($request->all()) for a student. You could move this to a synchronous job and pass the parent model and the validated data as constructor parameters, but that may be a bit overkill.

The second opportunity to DRY your code out would be the view. You could use the same view for both creating a school contact and a student contact, as I’m assuming they’d have the same fields. The only thing that would be different is the URL those forms would post to. As aforementioned, the fields (and therefore validation) would be the same across both.

Thanks to the both of you. I've also just seen the documentation about polymorphic relationships in the Laravel docs that helped to answer a few other questions I had!