Since 5.5 attribute casting works in both directions and it ruined my seeds when i updated to 5.5, I thought we should inform other developers about that issue, because it runs without an error, but when you access the attribute it will not cast back to array, because it was encoded twice...

Just added some more examples of results from various helper functions (mostly array ones). Every now and then I have to try to figure out which helper would be most appropriate, and the results give a clearer picture of the function.

This info is based on discoveries using Vite with an app running in Laravel Sail. I needed to call npm run dev from my host machine in order for HMR to work. Others mentioned similar issues with Homestead on the issue discussion here.

I have added the missing extensions Dom and Zip to the list. I removed Tokenizer from the list, since it is enabled by default since PHP 4.3. The reason is because it is not an extension that you can install, but a compile-time option (that is enabled by default.)

Without backslash Laravel will append namespace to main application namespace and will return an error "Class App\Http\Controllers\Laravel\Cashier\WebhookController does not exist".

See this discussion: http://laravel.io/forum/07-08-2014-editing-the-documentation-for-brevity-and-readability

I'd like to do this throughout the documentation where appropriate. Please let me know any feedback first. Thanks.

The line where it sets the VBoxInternal2/SharedFoldersEnableSymlinksCreate should also contain the path to the shared folder inside the VM. This is done in the last part where it originally says /v-root.

The shared folder in Homestead is: /home/vagrant/code.

Therefore the correct config should be:

   config.vm.provider "virtualbox" do |v|
        v.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/code", "1"]
    end

I updated one of my projects from 4.0 to 4.1. In reading the documentation, I instantly ran php artisan auth:reminders-controller to create my reminders. That resulted in an error because I hadn't run composer update yet. I thought that it would be nice to let others know not to run that until they are done upgrading.

Also, when I ran composer update, I saw some "Permission Denied" errors. I re-ran composer update this time with sudo and it all went fine.

Ravi.

whereHasMorph doesn't seems compatible with multiple database connections on models. I'm not entirely sure if this is a bug or a limitation. I tried to dig into the (Eloquent) query builder but couldn't figure out how to fix this.

It's around here where the constraints get applied: https://github.com/laravel/framework/blob/8eb1827d7290dba9c55e54fa296275eb6f4b491a/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php#L229-L230

So I opted to put it in the documentation for now.

I would like to propose to change User in the Generating Resources section example to UserResource to avoid conflict with the User model namespace when importing the User resource in the UserController.

This PR updates the required PHP version.

The version should most likely be 7.2.5: According to https://github.com/symfony/service-contracts/blob/master/composer.json it's the minimum required version for symfony contracts.

If the value of APP_SERVICE is not the application's image name (defaults to laravel.test), sail artisan ... commands results in error similar to service "laravel.test" is not running container #1

The php artisan cashier:webhook command creates a webhook which also listens for the invoice.payment_succeeded event. I've added it to the list to ensure people don't miss it when creating the webhook and adding events manually instead of using the command.

:warning: WIP

Waiting for:

• https://github.com/laravel/homestead/issues/1814
• https://github.com/laravel/homestead/issues/1819
• and maybe https://github.com/laravel/homestead/pull/1818 ?

@svpernova09

This PR removes the section on local sharing which was added to the documentation in https://github.com/laravel/docs/pull/5677. The reasoning for this removal is that the feature doesn't exist in Laravel Valet. If a user follows the steps outlined in the documentation they'll always get back the default Laravel Valet 404 not found page.

I'm not sure why it was added to the documentation, but it seems at least @driesvints knows this feature doesn't exist. Given issue (https://github.com/laravel/valet/issues/1093) was converted to a discussion for feature requests (https://github.com/laravel/valet/discussions/1143) instead of an issue.

There is also the following comment on another issue regarding local network access (https://github.com/laravel/valet/issues/440#issuecomment-579830736) where a user suggested a fix for getting local networking to work, but that requires changing internals for Laravel Valet.

As Laravel Valet is now there is no feature for local network sharing and the section can be removed.