Set up API router when first API routes are generated #728
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
In a clean installation of Laravel 11, the
routes/api.php
file is absent and not configured inbootstrap/app.php
. When Blueprint generates API routes, it creates the file, but the developer must manually edit it to add the PHP opening tag and theuse Illuminate\Support\Facades\Route;
line. They must also modifybootstrap/app.php
to enable that API route file.Changes
This PR updates Blueprint to check the following when creating API routes:
routes/api.php
file exists, creating it if necessary, using a basic stubbootstrap/app.php
, adding the configuration if missingThese actions occur before the addition of the generated API routes.
This PR takes inspiration from Laravel's ApiInstallCommand.
Testing
Tests to check this functionality has been added to
RouteGeneratorTest.php
.PS. No annoying WIPs this time! 😅