hatame/hatame.andarza09
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git add .

Browse Source 
git commit  "create admin panel layout with header sidebar and footer"
This commit is contained in:
hatame
2026-08-18 09:49:19 +03:30
parent 14684d5537
commit d7bd95f71a
39 changed files with 347 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
config/models.php
+9 -9
View File
@@ -353,23 +353,23 @@ return [
| How the relations should be named in your models.
|
| 'related' Use the related table as the relation name.
| (post.author --> user.id)
generates Post::user() and User::posts()
| (post.author --> userController.id)
generates Post::userController() and User::posts()
|
| 'foreign_key' Use the foreign key as the relation name.
| This can help to provide more meaningful relationship names, and avoids naming conflicts
| if you have more than one relationship between two tables.
| (post.author_id --> user.id)
| (post.author_id --> userController.id)
| generates Post::author() and User::posts_where_author()
| (post.editor_id --> user.id)
| (post.editor_id --> userController.id)
| generates Post::editor() and User::posts_where_editor()
| ID suffixes can be omitted from foreign keys.
| (post.author --> user.id)
| (post.editor --> user.id)
| (post.author --> userController.id)
| (post.editor --> userController.id)
| generates the same as above.
| Where the foreign key matches the related table name, it behaves as per the 'related' strategy.
| (post.user_id --> user.id)
| generates Post::user() and User::posts()
| (post.user_id --> userController.id)
| generates Post::userController() and User::posts()
*/
'relation_name_strategy' => 'related',
@@ -486,7 +486,7 @@ return [
// 'except' => ['migrations'],
// 'only' => ['users'],
// // Table Specifics Bellow:
// 'user' => [
// 'userController' => [
// // Don't use any default trait
// 'use' => [],
// ]