Question serviceProvider about livewire-flash

[Kixell-NicolasJardillier]

Moreover livewire-flash::alerts.base is based on previous commits, right ?

[mattlibera]

@nicoja You're correct that the last directive for \Blade::component can be removed, but the other things are necessary to make the package function. If you are unfamiliar with package authoring in Laravel, here's my quick explanation:

public function boot()
{
    // where to find config file if it is not published in app's `config` directory - loaded from this package
    $this->mergeConfigFrom(__DIR__. '/publish/livewire-flash.php', 'livewire-flash');

    // where to find views prefixed with `livewire-flash::`
    $this->loadViewsFrom(__DIR__ . '/views', 'livewire-flash');

    // what to publish when using `php artisan vendor:publish` and where to publish to.
    // in this case, would publish the `livewire-flash.php` config file to the app's `config` folder, if the developer wanted to customize it.
    $this->publishes([
        __DIR__ . '/publish' => config_path()
    ]);

    // registers Livewire components so that they can be found when using `@livewire` or `<livewire>` directives
    Livewire::component('flash-container', \MattLibera\LivewireFlash\Livewire\FlashContainer::class);
    Livewire::component('flash-message', \MattLibera\LivewireFlash\Livewire\FlashMessage::class);

    // old, unneeded in current version
    \Blade::component('livewire-flash::alert', 'livewire-flash::alerts.base');
}

I'll remove this in a quick hotfix PR.

[mattlibera]

Done in v0.4.1