[10.x] Adds make:view Artisan command

[nunomaduro]

This pull request adds the long-awaited make:view Artisan command. As expected, to get started, you simply have to type:

php artisan make:view users.index

INFO: View [resources/views/users/index.blade.php] created successfully.

Here are the contents of the resources/views/users/index.blade.php file. It's a very simple div with an inspirational quote inside:

<div>
    <!-- The best way to take care of the future is to take care of the present moment. - Thich Nhat Hanh -->
</div>

Regarding testing, we've created a custom "testing" stub for this make command. So, if users provide the --test option, they will see the following:

php artisan make:view users.index --test

INFO: View and test [resources/views/users/index.blade.php] created successfully.

And the test's contents:

<?php

namespace Tests\Feature\View\Users;

use Tests\TestCase;

class IndexTest extends TestCase
{
    /**
     * A basic view test example.
     */
    public function test_it_can_render(): void
    {
        $contents = $this->view('users.index', [
            //
        ]);

        $contents->assertSee('');
    }
}

When using the --pest option, they will see the following contents in the test:

<?php

it('can render', function () {
    $contents = $this->view('users.index', [
        //
    ]);

    $contents->assertSee('');
});

Finally, if users wish to have an extension other than blade.php, they can provide the --extension option:

php artisan make:view users.index --extension=php

INFO: View [resources/views/users/index.php] created successfully.

[svenluijten]

As author of sven/artisan-view, I wholeheartedly approve! 👍 While this doesn't have the ability to scaffold the contents of the view the same way my package does, I think it's fine to leave that up to the developer to do manually. Especially with things like Folio, Livewire, custom Blade components, etc. in the ecosystem now, it'd be difficult to find a balance for things to include and the options you'd have to add to this command would get out of hand pretty quickly.

And, FWIW, this would also close the highest voted issue on laravel/ideas! 🎉

[josedaian]

Hi @nunomaduro,

This is a very good feature!
I only have a doubt about the functions declarations. Is there some reason about don't add the return type into the function declaration?
I mean, not as a docblock.
For example:

protected function getNameInput(): string
{
}

It's just to know 😅.

Your work is incredible!