Pedro Cunha

Results 34 comments of Pedro Cunha

I see people in this bug report performing measurements on `vagrant version`, but that won't be accurate at all because it performs an HTTP request to Vagrant to fetch the...

Homestead Hyper-V for some reason has a 30 second delay on boot with GRUB. That's why it takes forever for `vagrant up` to get an IP from the machine.

Definitely something we'll implement. Just have to figure out how first. There's some partial support for custom URLs in the current version of Solder (0.7.6), but it isn't in a...

:warning: Shift found uses of the old `array()` syntax. Laravel adopted the short array syntax `[]` since it became available in PHP 5.4.

:warning: Shift found uses of the old `array()` syntax. Laravel adopted the short array syntax `[]` since it became available in PHP 5.4.

:warning: Shift found instances of string based class references. Laravel adopted the `::class` static property since it became available in PHP 5.5. You should update your code to use references...

:warning: The following controllers contain actions outside of the 7 resource actions (`index`, `create`, `store`, `show`, `edit`, `update`, `destroy`). For more details, review [the docs](https://laravel.com/docs/5.7/controllers#resource-controllers) or watch [Cruddy by Design](https://www.youtube.com/watch?v=MF0jFKvS4SI)...

:warning: Shift found inline validation in the following controllers. Unless you require this level of control, you should use a [Form Request](https://laravel.com/docs/validation#form-request-validation) to encapsulate this validation logic and keep your...

:warning: Shift detected the following HTTP components using the `Request` or `Input` facade to access the request. Within these components you should leverage the request object which is [automatically injected](https://laravel.com/docs/requests#accessing-the-request)...

:warning: Shift detected the following HTTP components accessing the authenticated user through `Auth::user()`. Within these components, you can access the authenticated user through the [request object](https://laravel.com/docs/5.7/authentication#retrieving-the-authenticated-user) as well. Doing so...