pyaesone17/laravel-pretty-handler

:package_description

1.0.1 2017-05-24 13:14 UTC

Requires

• php: ~5.6|~7.0
• illuminate/support: ~5.1

Requires (Dev)

• phpunit/phpunit: ~4.0||~5.0||~6.0
• squizlabs/php_codesniffer: ^2.3

MIT

• Pyae Sone Nyein

• pyaesone17
• laravel-pretty-handler

README

The package will allow you to define the error view based on model and based on the request.

Frontend view of Shop Model Not Found Exception

Backend view of Shop Model Not Found Exception

Install

Via Composer

$ composer require pyaesone17/laravel-pretty-handler

Usage

Firstly register the serviceprovider in config/app.php like this

   [ ....
       Pyaesone17\LaravelPrettyHandler\PrettyServiceProvider::class       
   ],

Resolve \Pyaesone17\LaravelPrettyHandler\PrettyHandler like this in the render method of App\Exceptions\Handler.

$prettyResponse = ( resolve(\Pyaesone17\LaravelPrettyHandler\PrettyHandler::class)) ($e);

if($prettyResponse){
    return $prettyResponse;
}

In the model you have to implement \Pyaesone17\LaravelPrettyHandler\Pretty trait and set up using setUp method.

prettyDefaultView will be default view of the App\User not found exception.

prettyRules will accept the array list with url and view.

In the following example, if the exception occurs in admin section errors.backend page will show.

If request does not match any url value, it will show default page of the Model that is defined in prettyDefaultView.

class User extends Model
{
    use Pretty;

    public function setUpPretty()
    {
        $this->prettyDefaultView = 'errors.coming';
        $this->prettyRules = [
            ['url' => 'admin/*','view' => 'errors.backend'],
            ['url' => 'frontend/*','view' => 'errors.frontend'],
            ['url' => 'shop/*', 'view' => 'errors.coming']
        ];
    } 
}

Note

Do not use \Pyaesone17\LaravelPrettyHandler\PrettyHandler::class directly in Handler because it recieve constructor value from the Service Container.

You have to resolve the class fromn the container.

Change log

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING and CONDUCT for details.