You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could it be possible to enforce the usage of a base Model class that is in the user space and not in de vendor directory.
for example.
I use the jensseger mongodb package which extends the base model. But all the tools ( like telescope) have a direct usage of Illuminate\Database\Eloquent\Model. So to get that to work i have to override the file Laravel\Telescope\Storage\EntryModel in the vendor folder. Which, offcourse is a no-no.
If we could create a base model in say "\App\Models\BaseModel.php" which extends Illuminate\Database\Eloquent\Model.
Then we could create more flexibility with very little effort...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Could it be possible to enforce the usage of a base Model class that is in the user space and not in de vendor directory.
for example.
I use the jensseger mongodb package which extends the base model. But all the tools ( like telescope) have a direct usage of Illuminate\Database\Eloquent\Model. So to get that to work i have to override the file Laravel\Telescope\Storage\EntryModel in the vendor folder. Which, offcourse is a no-no.
If we could create a base model in say "\App\Models\BaseModel.php" which extends Illuminate\Database\Eloquent\Model.
Then we could create more flexibility with very little effort...
Beta Was this translation helpful? Give feedback.
All reactions