Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.x] PhpStorm fixes + improvments #31700

Closed
wants to merge 2 commits into from
Closed

Conversation

voku
Copy link
Contributor

@voku voku commented Mar 3, 2020


This change is Reviewable

voku added 2 commits March 3, 2020 00:56
- fix phpdocs
- add static (for anonymous functions, less for for PHP and for the IDE, because $this is not allowed)
- use some more modern phpdocs (e.g. array => Model[])
- use php7 features like "array-unpacking"
- replace "call_user_func" (laravel#29932 <- the test did not fail, but maybe I missed something here)
- use "array_values()" only if needed
* upstream/6.x: (21 commits)
  Revert "[6.x] migrate --seed should seed the same database (laravel#31678)" (laravel#31685)
  [6.x] Allow easier customization of the queued mailable job (laravel#31684)
  [6.x] migrate --seed should seed the same database (laravel#31678)
  [6.x] Make newPivotQuery public (laravel#31677)
  [6.x] update changelog
  Fix flakey memcached tests (laravel#31646)
  Fixed phpdoc
  formatting
  [6.x] Expose Notification Id within Message Data (laravel#31632)
  [6.x] Add support for Arr::hasAny (laravel#31636)
  Fix phpdoc
  [6.x] update changelog
  [6.x] update changelog
  Fix styling for phpdoc
  Create resolve method which loads deferred providers if needed
  Revert "Call make instead of resolve to load deffered providers"
  Call make instead of resolve to load deffered providers
  Add test that failes to load deffered provider of implementation while accessing class through interface
  Use correct locale when resolving Faker from the container (laravel#31615)
  clean-up-some-methods
  ...

# Conflicts:
#	src/Illuminate/Database/DatabaseServiceProvider.php
@taylorotwell
Copy link
Member

I'm sorry, I think I said before I can't merge these huge PRs. It takes too long to review them all. A better approach would to be break it up by component and send them to me one at a time as I merge them.

Especially the night before a major release.

Some of these are formatting changes we wouldn't even accept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants