Download the PHP package devil999/solidgenerator without Composer

Package: devil999/solidgenerator:

 Solid Generator generates solid code with controller api resources, custom request, with repo pattern, migrations based on model_schema_json file  with admin panel for blade etc..
 Note: For better result: 
        Think to design software and write your schema 
        according in model_schema_json.json file formate stored in root path and run solid:make commands 
    AdminLte is being used for admin panel/dashboard:
    Laravel breeze for Auth is necessary:
    Analyse the output files and complete your project with ease.

For collaboration or contribution: Mail to: [email protected]

Initial Required packages:

laravel breeze, spatie (for roles, logs, etc,)
installation:
        composer require laravel/breeze --dev  OR php artisan breeze:install blade
        composer require spatie/laravel-permission

Register Service Provider :

Laravel 11 :
        Add :    SolidPrincipleServiceProvider::class to bootstrap/providers.php
    Laravel 10 : Find you self 

Public solid-generator assets :    php artisan vendor:publish --tag=solid-app
Globle :   php artisan solid:make --publish

Help: php artisan solid:make -h

Operations:

Role and permission (options)
Steps: 1)(Optional): Add: 
        the below code in app/Providers/AuthServiceProvider.php inside boot function at last</br>  
        Gate::before(function ($user, $ability) {</br>  
            return ($user->super_admin == 1 && $user->status == 1) ? true : null;</br>  
       });

    For laravel 10:
        Steps: 2): Add: following inside app/Kernel inside: protected $routeMiddleware = [] at last, like</br>
        protected $routeMiddleware = [</br>
        '...'=>'...',</br>
        '...'=>'...',</br>
        '...'=>'...',</br>
        'role' => \Spatie\Permission\Middlewares\RoleMiddleware::class,</br>
        'permission' => \Spatie\Permission\Middlewares\PermissionMiddleware::class,</br>
        'role_or_permission' => \Spatie\Permission\Middlewares\RoleOrPermissionMiddleware::class,</br>
        ]</br> 
    For laravel 11: find spatie way to add middleware alias 

        Steps: 3) Add: trait 'HasRoles' in User Model;

        Steps: 5) Seed:  UserRolePermissionSeeder; command here <br>  php artisan db:seed --class=UserRolePermissionSeeder

First test command after setup :

php artisan solid:make --crud 

// This will Generates Following files: Example for api enabled and repo design patter, Vary in Configuration you provides

1. Traits FileManager.php . // to manage file uploading
2. Traits Api_Response.php . // to manage api response
3. Interfaces SolidInterface.php File. 
4. Repositories SolidBaseRepository.php File.
5. Models DemoProduct.php File.
6. Repositories DemoProductRepository.php File.
7. API CreateDemoProductRequest.php File.
8. Controllers DemoProductController.php File.
9. migrations 2025_02_02_070024_create_demoproducts_table.php File.
Resources:  
    10. DemoProductListResource.php File.
    11. DemoProductCreateResource.php File.
    12. DemoProductShowResource.php File.
    13. DemoProductEditResource.php File.

Notice incide configuration file:   'design_pattern'=> "repository", //Design patterns are : none or repository

Global function :

app('sidebar')

Commands: (depends on solid configuration file)

  php artisan solid:make {model_name? : Optional model_name parameter}

             {--config|config : Generate Package configuration }
             {--crud|crud : Generate Plain CRUD files }
             {--api|api : Generate api resources}
             {--repo-crud|repo-crud : Generate CRUD files for Repository design pattern }
             {--m|model : Generate model}
             {--view|view : Generate model}
             {--c|controller : Generate Controller }
             {--i|interface : Generate interface}
             {--re|repo  : Generate repository}
             {--mi|migration  : Generate migration}
             {--r|request : Generate custom request}
             {--ro|route : Generate routes}
             {--layout|layout  } layout_type? : Generate Layout}
             {--newAdminPanel|new-admin-panel : Generate fresh Admin panel}
             {--publish|publish : Generate Publish files }
             {--h|help}
             {--t|test}

Config : config/solid.php

////////////////////////////////////////////////////////////////////////////
//                                                                        //
//                   WARNING :  DEVIL000/SOLID - PACKAGE                  //
//            DO NO ALTER DEFAULT CONFIGURATION UNLESS REQUIRED           //
//                   ALTERING HERE MAY CAUSE MALFUNCTION                  //
//                                                                        //
////////////////////////////////////////////////////////////////////////////
//--NOTE:NOTE--//
////////////////////////////////////////////////////////////////////////////
//                                                                        //
//         All Directory Name pattern should match the pattern below      //
//                                                                        //
////////////////////////////////////////////////////////////////////////////

'modular_app'=>false, // If the app is built on top of module based system design. (Coming soon...)
'model_schema_json_path' => base_path("model_schema_json.json"),  // root path/base_path
'is_api' => true,  // Is this application is developing an api's.
'api_with_resource_classes'=>true,  // Depends on is_api, This will create an api resources for models if is_api is true.
'react_with_inertia'=>false, // coming soon...
'model_path' => "app/Models",
'controller_path' => "app/Http/Controllers",
'api_resources_path' => "app/Http/Resources",
'request_path'=>"app/Http/Requests",
'view_path' =>"resources/views",  // When is_api is true this will be disabled automatically.
'migration_path'=>"database/migrations", // Migration Path
'seeder_path'=>"database/seeders",   // Seeder Path
'backend_admin_view_path' => "resources/views/backend/admin",  // Storage for View files of Admin/backend.
'frontend_view_path' => "resources/views/frontend",  // Storage for View files of Frontend.
// Configuration for Repository design pattern
'design_pattern'=> "repository", //Design patterns are : none or repository
'interface_path' => "app/Interfaces",  // Interface Path
'repo_path' => "app/Repositories",   // Repository Path
'base_interface_name' => "SolidInterface",  // Base Interface name
'base_repository_name' => "SolidBaseRepository",  // Base Repository name
// Other Configuration
'show_file_already_exists_warning' => false,  //
'show_folder_already_exists_warning' => false,
// Override created file : This may delete the contents of previous file generated by SOLID (Not applied Yet)
'override_previous_file_data' => false,
"carbon_immutable" => true

Bugs:

1. By default, the middlware function are applied in Controller files 
   you need to remove it manually if you dont use auth and spatie permission package

Sidebar Configuration Documentation

This documentation describes how to use the SideBar::add() OR route: localhost://sidebar method to create a custom sidebar configuration with multiple options, including sub-links, icons, visibility, permissions, and active routes.

Sidebar Configuration Example

Adding a Sidebar

The following example demonstrates how to add a "Product" on sidebar with its associated sub-links:

php

Breakdown of the Configuration

Adding Sidebar:

• SideBar::add('Product'): This creates a new sidebar item titled "Product".

Sidebar Properties:

• ->group('Purchase'): Sets the sidebar item’s icon using Font Awesome. Here, it uses the "fa-product-hunt" icon.
• ->icon('fa-brands fa-product-hunt'): Sets the sidebar item’s icon using Font Awesome. Here, it uses the "fa-product-hunt" icon.
• ->route(''): Defines the route for the sidebar item. In this case, the route is left blank, which can be configured based on your needs.
• ->title('Product'): The title that appears on the sidebar. It is set as "Product".
• ->hide(true): Specifies that the sidebar item is visible. Set to true to make it visible.
• ->permission(true): Specifies that the sidebar item is available for users with permission. Set to true to allow access.
• ->activeOnRoutes('admin/products/mainSidebar'): Defines the route(s) where this sidebar item should be marked as active. In this case, it is active when the route matches admin/products/mainSidebar.

Sub Links

The sidebar item can have multiple sub-links. These sub-links are defined using the subLinks() method.

Add Product Sub-Link:

php

• SubLink::add('Add Product'): Creates a sub-link titled "Add Product".
• ->icon('fa-solid fa-plus'): Sets the icon for the sub-link. In this case, it's a plus icon.
• ->route('/admin/products/route_create11'): Specifies the route for this sub-link.
• ->hide(true): Makes the sub-link visible.
• ->permission(true): Grants permission for the sub-link.
• ->activeOnRoutes('/kaushala/products/active_on_create1'): Marks the sub-link as active for the specified route.

List Products Sub-Link:

php

• SubLink::add('List Products'): Creates another sub-link titled "List Products".
• ->icon('fa-solid fa-list'): Sets the icon for the sub-link as a list icon.
• ->route('/admin/products/route_create'): Specifies the route for the "List Products" sub-link.
• ->hide(true): Ensures the sub-link is visible.
• ->permission(true): Grants permission for the sub-link.
• ->activeOnRoutes(['hari/admin/products+a']): Marks the sub-link as active for the specified route(s).

Method Details

SideBar::add($name)

• Description: Adds a new sidebar item.
• Parameters:
  • $name: The title of the sidebar item (e.g., 'Product').

->icon($icon)

• Description: Sets the icon for the sidebar item.
• Parameters:
  • $icon: The Font Awesome class for the icon (e.g., 'fa-brands fa-product-hunt').

->route($route)

• Description: Defines the route for the sidebar item.
• Parameters:
  • $route: The route URL for the sidebar item (can be a string or a route name).

->title($title)

• Description: Sets the title text that will be displayed for the sidebar item.
• Parameters:
  • $title: The title of the sidebar item (e.g., 'Product').

->hide($hide)

• Description: Controls the hide of the sidebar item.
• Parameters:
  • $hide: true to make the item visible, false to hide it.

->permission($permission)

• Description: Determines whether the sidebar item is accessible based on user permissions.
• Parameters:
  • $permission: true if the item is accessible, false if not.

->activeOnRoutes($routes)

• Description: Defines the routes where the sidebar item will be marked as active.
• Parameters:
  • $routes: A string or an array of route names or URLs.

subLinks($subLinks)

• Description: Adds sub-links to the sidebar item.
• Parameters:
  • $subLinks: An array of SubLink instances, each representing a sub-link.

SubLink Configuration

Example SubLink Method:

php

SubLink Method Details:

• SubLink::add($name): Adds a sub-link with the specified name.
• ->icon($icon): Sets the icon for the sub-link.
• ->route($route): Defines the route for the sub-link.
• ->hide($hide): Controls the visibility of the sub-link.
• ->permission($permission): Specifies whether the sub-link is available based on permissions.
• ->activeOnRoutes($routes): Marks the sub-link as active for the given route(s).

Blade Code for Frontend here:

JS Code for frontend

Future Implementation Grouping like this. coming soon...

Data formate

`

For local development

`

Filter params required from frontend

`