From v3 of Spatie DTO package seem that fromRequest() it's not anymore the way to be used.

I checked readme of v2 and I found it, but in v3 it's not anymore there.

As https://github.com/regnerisch/laravel-beyond/issues/54 requested, I have created beyond:make:trait command.

The trait is created in Domain\XXX\Traits namespace by default. You can add --support flag to create the trait in Support\Packages\Laravel\Traits namespace.

As discussed here https://github.com/regnerisch/laravel-beyond/pull/58 this PR add a new optional flag --factory in DTO command. When added will be create a new class in App for DTO Factory.

Usage:

# Will ask Domain, Class name and App
beyond:make:dto --factory

# Will ask App and create the factory in 
# `src/App/Web/User/DataFactories/UserDataFactory.php` (Supposely App provided is "Web")
beyond:make:dto User/UserData --factory

A DTO like this:

<?php

namespace Domain\Users\DataTransferObjects;

use Spatie\DataTransferObject\DataTransferObject;

class MyData extends DataTransferObject
{
    // Add properties here
}

Will create a DTO Factory:

<?php

namespace App\Admin\Users\DataFactories;

use Illuminate\Http\Request;

use Domain\Users\DataTransferObjects\MyData;

class MyDataFactory
{
    public static function fromRequest(Request $request): MyData
    {
        return new MyData($request->all());
    }
}

Currently commands are restricted to beyond:make:command {schema}. We should provide an alternative way since not everybody is used to "Laravel Beyond CRUD" and may not know the schema.

• php artisan beyond:make:model should ask for Domain and Class Name and creates a class based on these information

Hello,

when setting up the project I get the prompt to add something to the boot method of my AppServiceProvider.

1. Which exact namespace is this Factory? There are multiple ones provided by Laravel.
2. Why is this not automatically added?

Instead of adding for each controller the default Laravel traits for controller, would be better to keep the default Laravel controller as Base controller and then extend it.

So the controller.stub would be:

<?php

namespace App\{{ namespace }}\Controllers;

use Support\Packages\Laravel\Controllers\Controller;

class {{ className }} extends Controller
{
    // Methods here...
}

And we can add the base controller for example inside Support/Packages/Laravel/Controller with default content:

<?php

namespace Support\Packages\Laravel\Controllers;

use Illuminate\Foundation\Auth\Access\AuthorizesRequests;
use Illuminate\Foundation\Bus\DispatchesJobs;
use Illuminate\Foundation\Validation\ValidatesRequests;
use Illuminate\Routing\Controller as BaseController;

class Controller extends BaseController
{
    use AuthorizesRequests, DispatchesJobs, ValidatesRequests;
}

Would you be interested in adding this package for action:

https://github.com/spatie/laravel-queueable-action

As replacement for current MakeActionCommand, or as a new one.

Command signature would be:

beyond:make:qa {name?} {--overwrite} {--queueable}

or in case as replacement for current Action:

beyond:make:action {name?} {--overwrite} {--queueable}

I am tempted also by this package https://laravelactions.com/ but maybe it's too much, even if can be cherry pick what you want from it, https://laravelactions.com/2.x/granular-traits.html#cherry-picking

Also not sure how if this can be even combined with DDD.

What you think?

I read only the free blog of laravel beyond, so maybe this is explained in the paid book.

I see that we can use flag --support for middleware and rule, and this add them inside Support/Packages/Laravel.

For example if I create a middleware with --support this is created in:

Support/Packages/Laravel/Middleware

Why inside "Laravel" folder and not in Support/Middleware?

Also there is already a folder Support/Packages/Laravel/Middlewares (with final "s"), while our middleware is created inside Support/Packages/Laravel/Middleware (without "s").

As I can read about Support namespace in the blog article "as the dumping ground for all little helpers that don't belong anywhere". So not sure why everything it's under "Support/Packages/Laravel" and not directly inside "Support/Middleware", etc..

Not sure if for questions like this there is another place.

Thanks

Laravel Beyond Crud has the concept of Builders. They aren’t yet implemented I think as the query command of this package is for another things, isn’t it?

Hi, thank you for this package, this is what I wanted for so long!

I created a new Command: php artisan beyond:make:command CreateUserTokenCommand

This command does not appear automatically when I do php artisan list.

Maybe i'm wrong but after some research, it seems because load($paths) into Illuminate\Foundation\Console\Kernel tries to remove a part of the file path with app_path():

$command = $namespace.str_replace(
    ['/', '.php'],
    ['\\', ''],
    Str::after($command->getRealPath(), realpath(app_path()).DIRECTORY_SEPARATOR)
);

But it doesn't work, because app_path returns /Users/dimzeta/Sites/laravel/app while the real app path should be /Users/dimzeta/Sites/laravel/src (Is it correct ?)

EDIT:

As soon as I use base_path('src/App') instead of app_path() it's working well. But maybe this is not the right way, because we still have a wrong path using app_path() ?

Hi, Currently, there is an error when we copy and paste the given code block to AppServiceProvider. This will fix the following errors:

1. syntax error, unexpected identifier "Factory", expecting ";" at src/App/Providers/AppServiceProvider.php:27
2. Class "App\Providers\Illuminate\Database\Eloquent\Factories\Factory" not found at src/App/Providers/AppServiceProvider.php:26 Thanks

Just like #37 based on Ryutu Hamasakis talk at Laracon Online Winter 2022 (https://youtu.be/0Rq-yHAwYjQ?t=5885 -> link now with different timestamp than before): To seperate the domain boundaries we could use deptrac and maybe add this to the default template. What do you think?