Configuration

Publishable assets

Note

Publishing the package assets is optional and you are not required to do this if you don't need to.

Tag	Publishes
better-laravel-config	config/better-laravel.php
better-laravel-views	resources/views/vendor/better-laravel
better-laravel-stubs	resources/stubs/vendor/better-laravel
better-laravel	All of the above

Config

You may run the following command to publish the configuration file.

php artisan vendor:publish --tag=better-laravel-config

Following is the default configuration file, and you are free to update the values as per your need.

return [
    'enable_routes' => env('BETTER_LARAVEL_ENABLE_ROUTES', true),
    'web_routes_prefix' => env('BETTER_LARAVEL_WEB_ROUTES_PREFIX', ''),
    'api_routes_prefix' => env('BETTER_LARAVEL_API_ROUTES_PREFIX', 'api'),
];

Option	Env	Default	Action
enable_routes	BETTER_LARAVEL_ENABLE_ROUTES	true	Should the package load routes from routes/api & routes/web?
web_routes_prefix	BETTER_LARAVEL_WEB_ROUTES_PREFIX	''	Prefix for routes registered under routes/web
api_routes_prefix	BETTER_LARAVEL_API_ROUTES_PREFIX	'api'	Prefix for routes registered under routes/api

When enable_routes is on, the service provider loads every .php file under routes/web (recursively, in sorted order) with the web middleware group and every .php file under routes/api with the api middleware group. Routes are registered in the provider's boot() method and are skipped when the application's routes are cached (php artisan route:cache), since the cache already contains them.

Views

php artisan vendor:publish --tag=better-laravel-views

The package ships a single better-laravel::welcome view, which generated route files return as a placeholder.

Stubs

php artisan vendor:publish --tag=better-laravel-stubs

The generator commands read their stubs from resources/stubs/vendor/better-laravel when a published copy exists and fall back to the package stubs otherwise. The stubs are controller.php.stub, feature.php.stub, operation.php.stub, request.php.stub, job.php.stub, job.queueable.php.stub and route.php.stub. route.php.stub receives (for example v1/blogs, without a leading slash) plus and (with a leading slash), so route stubs published before v4 keep working.