mirror of
				https://github.com/invoiceninja/invoiceninja.git
				synced 2025-10-31 09:47:31 -04:00 
			
		
		
		
	Shift automatically applies the Laravel coding style - which uses the PSR-2 coding style as a base with some minor additions. You may customize the code style applied by adding a [PHP CS Fixer][1] or [PHP CodeSniffer][2] ruleset to your project root. Feel free to use [Shift's Laravel ruleset][3] to help you get started. For more information on customizing the code style applied by Shift, [watch this short video][4]. [1]: https://github.com/FriendsOfPHP/PHP-CS-Fixer [2]: https://github.com/squizlabs/PHP_CodeSniffer [3]: https://gist.github.com/laravel-shift/cab527923ed2a109dda047b97d53c200 [4]: https://laravelshift.com/videos/shift-code-style
		
			
				
	
	
		
			71 lines
		
	
	
		
			2.5 KiB
		
	
	
	
		
			PHP
		
	
	
	
	
	
			
		
		
	
	
			71 lines
		
	
	
		
			2.5 KiB
		
	
	
	
		
			PHP
		
	
	
	
	
	
| <?php
 | |
| 
 | |
| return [
 | |
|     /*
 | |
|      * Enable or disable the query detection.
 | |
|      * If this is set to "null", the app.debug config value will be used.
 | |
|      */
 | |
|     'enabled' => env('QUERY_DETECTOR_ENABLED', false),
 | |
| 
 | |
|     /*
 | |
|      * Threshold level for the N+1 query detection. If a relation query will be
 | |
|      * executed more then this amount, the detector will notify you about it.
 | |
|      */
 | |
|     'threshold' => (int) env('QUERY_DETECTOR_THRESHOLD', 3),
 | |
| 
 | |
|     /*
 | |
|      * Here you can whitelist model relations.
 | |
|      *
 | |
|      * Right now, you need to define the model relation both as the class name and the attribute name on the model.
 | |
|      * So if an "Author" model would have a "posts" relation that points to a "Post" class, you need to add both
 | |
|      * the "posts" attribute and the "Post::class", since the relation can get resolved in multiple ways.
 | |
|      */
 | |
|     'except' => [
 | |
|         //Author::class => [
 | |
|         //    Post::class,
 | |
|         //    'posts',
 | |
|         //]
 | |
|     ],
 | |
| 
 | |
|     /*
 | |
|      * Here you can set a specific log channel to write to
 | |
|      * in case you are trying to isolate queries or have a lot
 | |
|      * going on in the laravel.log. Defaults to laravel.log though.
 | |
|      */
 | |
|     'log_channel' => env('QUERY_DETECTOR_LOG_CHANNEL', 'daily'),
 | |
| 
 | |
|     /*
 | |
|      * Define the output format that you want to use. Multiple classes are supported.
 | |
|      * Available options are:
 | |
|      *
 | |
|      * Alert:
 | |
|      * Displays an alert on the website
 | |
|      * \BeyondCode\QueryDetector\Outputs\Alert::class
 | |
|      *
 | |
|      * Console:
 | |
|      * Writes the N+1 queries into your browsers console log
 | |
|      * \BeyondCode\QueryDetector\Outputs\Console::class
 | |
|      *
 | |
|      * Clockwork: (make sure you have the itsgoingd/clockwork package installed)
 | |
|      * Writes the N+1 queries warnings to Clockwork log
 | |
|      * \BeyondCode\QueryDetector\Outputs\Clockwork::class
 | |
|      *
 | |
|      * Debugbar: (make sure you have the barryvdh/laravel-debugbar package installed)
 | |
|      * Writes the N+1 queries into a custom messages collector of Debugbar
 | |
|      * \BeyondCode\QueryDetector\Outputs\Debugbar::class
 | |
|      *
 | |
|      * JSON:
 | |
|      * Writes the N+1 queries into the response body of your JSON responses
 | |
|      * \BeyondCode\QueryDetector\Outputs\Json::class
 | |
|      *
 | |
|      * Log:
 | |
|      * Writes the N+1 queries into the Laravel.log file
 | |
|      * \BeyondCode\QueryDetector\Outputs\Log::class
 | |
|      */
 | |
|     'output' => [
 | |
|         //\BeyondCode\QueryDetector\Outputs\Alert::class,
 | |
|         \BeyondCode\QueryDetector\Outputs\Log::class,
 | |
|         //\BeyondCode\QueryDetector\Outputs\Json::class,
 | |
|     ],
 | |
| ];
 |