Custom model methods |
Hey guys.
I'm working on a fairly new project, which is storing all setings in a MySQL table (myproject_settings). There are many cases where I need to fetch a single setting, using something like the following: PHP Code: $this->settings = new \App\Models\SettingsModel(); As you can see, having dozens of those lines throughout my project looks way too verbose. So I was thinking about adding a method to my model directly: PHP Code: class SettingsModel extends Model { And then, in my controller, I could just do: PHP Code: $mysetting = $this->settings->getSetting('mysetting'); My question is.. Is it bad practice to add custom methods directly in the model? I couldn't find anything related on the documentation. Thank you.
Thank you, guys.
Today I was reading the docs again, and I found in the provided example that it actually encourages using methods inside the model (https://codeigniter4.github.io/userguide...ction.html) Sorry for the ignorance, the doc is a bit messy ![]()
|
Welcome Guest, Not a member yet? Register Sign In |