Laravel Naming Conventions | Laravel | Page 1

still basin Oct 12, 2023, 10:08 PM

#

I am using a repository and service pattern, conventionally, what should I call the destroy method in each class?
Controller => destroy()
Service => destroyPost()
Repository => delete()
Or do you name all the same?

gentle salmon Oct 13, 2023, 8:30 AM

#

Naming things would usually be done with the same concepts. Like you have a PostService class, then having a method destroyPost doesn't make much sense, as the method is already defined in a class that describes what it's about

vestal hearth Oct 13, 2023, 8:53 AM

#

I really dislike using the same function names everywhere due to searchability/replaceability so I use

Controller => destroy()
Service => makePerish()
Repository => obliterate()

/s

#

We do destroy (controller) -> destroy (service) -> delete (repository)

#

Still not a fan of using destroy twice, but alas

still basin Oct 13, 2023, 5:09 PM

#

vestal hearth I really dislike using the same function names everywhere due to searchability/r...

what's stopping us from using these names

vestal hearth Oct 13, 2023, 5:18 PM

#

still basin what's stopping us from using these names

Nothing much really. I think using naming conventions in controllers is probably useful because of certain scaffolding using these names as well

#

Basically this in the docs: https://laravel.com/docs/10.x/controllers#actions-handled-by-resource-controller

Laravel - The PHP Framework For Web Artisans

Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.

#

Not sure if there is auto-discovery as well, so I'd definitely use these names for your controller functions

#

Service and repository? Nothing official on naming, I believe

#

Personally for repositories I like using the sql syntax as function name

#

Delete, insert, update etc

#Laravel Naming Conventions