genealabs/laravel-whoops-atom

This package is abandoned and no longer maintained. No replacement package was suggested.

Open Whoops Stack Trace in Atom Editor.

0.2.1 2018-01-03 00:06 UTC

Requires

• php: >=7.0.0
• illuminate/support: >=5.5.25

Requires (Dev)

• laravel/laravel: >=5.5.22
• mockery/mockery: 0.9.*
• phpmd/phpmd: ^2.6
• phpunit/phpunit: 5.7.*
• satooshi/php-coveralls: *
• sebastian/phpcpd: *

MIT

• Mike Bronner

README

Whoops-Atom for Laravel

Goal

Provide a method to open stack trace files from the Whoops error page, like is available for some other editors.

Installation

Dependencies

• Laravel 5.5.25 or greater
• PHP 7.0.0 or higher
• Atom Open Package

1. Install the package:

   composer require genealabs/laravel-whoops-atom --dev

2. Install Atom Open package.

Configuration

/*
|--------------------------------------------------------------------------
| Local Sites Path
|--------------------------------------------------------------------------
|
| Specify the local development folder that is synchronized with Homestead.
| If you are not using Homestead, set this to an empty string or null.
| This corresponds to the `-map:` line under `folders` in your
| `Homestead.yaml` file.
|
| Default: ~/Code (string|null)
|
*/
'local-sites-path' => '~/code',

/*
|--------------------------------------------------------------------------
| Homestead Sites Path
|--------------------------------------------------------------------------
|
| Specify the base path where Homestead stores the synced folder with your
| web sites. If you are not using Homestead, set this to an empty string
| or null. This corresponds to the `to:` line under `folders` in
| your `Homestead.yaml` file.
|
| Default: /home/vagrant/Code (string|null)
|
*/
'homestead-sites-path' => '/home/vagrant/code',

Only publish the config file if you need to customize it:

php artisan whoops-atom:publish --config

Usage

Warning: this package inserts a closure into a configuration setting. As this is intended for development environments only. To work with this, we recommend that you don't cache your config settings in your dev environment.

That was it! It will apply itself automatically to your application configuration.