Good morning!!!

I'm sorry, but my english is not good.

When I create a relationship between two models and schematics it implements it in the code of the corresponding model, it does it between the namespace declaration zone and the class, it does not add it to the end of the class, as would be correct. That must be defined somewhere or is it a bug?

And then, I have a problem with the migrations...

Please, anyone helps me?

Hello,

eager to try the package. Actually I have multiple namespaces and can't make schematics to read them. I need to set the config for each individual package. Since some packages make use of others I can't make them appear on the interface.

Can I trick schematics to scaffold a "base" namespace, so it finds the "models" in there?

Edited: The config only affects new models forms etc... the scaffolding is not working right now.

I'm using https://github.com/nWidart/laravel-modules, nothing fancy, just a way to divide the code into components, 100% laravel way. But still...

LogicException

at vendor/laravel/framework/src/Illuminate/Routing/Route.php:1039 1035| */ 1036| public function prepareForSerialization() 1037| { 1038| if ($this->action['uses'] instanceof Closure) {

1039| throw new LogicException("Unable to prepare route [{$this->uri}] for serialization. Uses Closure."); 1040| } 1041| 1042| $this->compileRoute(); 1043|

  +32 vendor frames

33 artisan:37 Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

I created "User hasMany Posts" relationship this is what the User.php file look like after that:

    /**
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function posts()
    {
        return $this->hasMany(\App\Models\Post::class);
    }
}

namespace App;

use Illuminate\Contracts\Auth\MustVerifyEmail;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;

class User extends Authenticatable
{
    use Notifiable;

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name', 'email', 'password',
    ];

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];

    /**
     * The attributes that should be cast to native types.
     *
     * @var array
     */
    protected $casts = [
        'email_verified_at' => 'datetime',
    ];
}

web.php

Route::get('/welcome', function () {
    return view('welcome');
});

 php artisan schematics:install

Error:

 Unable to prepare route [welcome] for serialization. Uses Closure.

  at /var/www/app/vendor/laravel/framework/src/Illuminate/Routing/Route.php:917

Hello, how are you? First of all I want to thank you for the beauty you are doing, it is very good!

But I followed the steps of installing the project, and here it gave this error:

If anyone knows how to proceed, please :) thanks in advance.

Great package 👏👏👏

Is there a way to run schematics on during development, when config('app.env') != 'production'?

Hi, it's an interesting project but it's not working anymore after trying fews things, now i only get this message when i acces to it.

Symfony\Component\ErrorHandler\Error\FatalError Cannot declare class App\Policies\User because the name is already in use``

Thanks.

This might be too edge case, but I recently started using a Laravel boilerplate which places the Models inside a non-standard location (src/App/) due to using Domain Driven Design pattern..

Any ideas on supporting a site structure like this? Thanks

Bumps url-parse from 1.5.1 to 1.5.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Hi, good job

I use https://nwidart.com/laravel-modules/v6/introduction to make modules in Laravel

Example: all modules are created into Modules folder, can set custom path to create a model into path Modules/Customer/Entities?? and are same case to create controller with namespace Modules\Customer

Another question is can use some iframe or something to put schematics into own view to seem it's into my system?? To see my layout with sidebar, navbar, footer and into content area see schematics

My layout

My layout + schematics

Thanks

Have suport for laravel 8?

As the subject says, schematics can find the migrations, but no models. We have written our code so that the routes are in devolved routes files - the code is separated into different modules, and each module has its own route file (eg Modules/Communication/Http/routes.php). Is there any way schematics can use this? The routes have been cached, and I can see them when I do php artisan route:list.

Thanks.

Hello,

In my tests, when adding a Model and check "Resource Controller" it does add a Controller in the Controllers folder but it doesn't contain CRUD methods.

Work in progress. Some things that need to be done from top of my head:

• FE should check model exists.
• When pivot model fields are left empty, should use default.
• BelongsToMany relations are now 'pseudo-relations' in backend (A related to AB, AB related to A). Maybe would be better if these 'pseudo-relations' exist in frontend only, because they are only there for visuals, and aren't actual model relations. They are not stored though (outside of cache) so maybe it's fine this way.
• Migrations for relations when generating pivot model with relations.
• General clean, not all parts are 'equally elegant'. Also some TODOs can be found in the wild
• I think belongsToManyMigrations dont delete correctly when the checkbox is used

When creating a model, choose a sub namespace, For example

Namespace = Blog Model = Post

App\Blog\Post.php App\Http\Controllers\Blog\PostController.php App\Http\Request\Blog\Post\CreatePostRequest.php

Namespace = Blog Model = Comment

App\Blog\Comment.php App\Http\Controllers\Blog\CommentController.php App\Http\Request\Blog\Comment\CreateCommentRequest.php

When creating a model you can rename the table ($ protected $ table = '' and Schema :: table () / Schema :: create ())