Phpinspectionsea: How to resolve transitive dependencies with Laravel

[rentalhost]

I am receiving a lot of warnings about transitive dependencies because of the usage of Laravel Illuminate classes. I am not understanding the reason of this warnings, once that I am requiring the laravel/framework (that implements this classes).

[rentalhost]

For some reason too, some classes are not being affected:

That is my composer.json:

[kalessil]

The marked classes are not coming from laravel/framework, but e.g. from illuminate/auth, illuminate/cache and etc.

Adding them implicitly would be the way to go - the implicit declaration of dependencies.
Might be redundant, but why not.

[kalessil]

I'll check if I can fix this

[rentalhost]

Hmm... Maybe it should consider the replace key from composer? Because the Laravel replace have a lot of instructions about that. I believe that it works like an "alias" to the package. So illuminate/auth refers to the own laravel/framework that I have set on my composer.json. If I am right, I guess that this warning is a false-positive.

[kalessil]

@rentalhost : all correct - that's a false-positive and we need to lookup the replace section in some cases.

[kalessil]

Solved in #890. I'll be possible to add 'laravel/*' into ignored packages.

[rentalhost]

Do you not prefer make this option configurable via options list?

[rentalhost]

Oh, you did it. :D

[kalessil]

Yep =)

[aand18]

Hello,
it still doesn't work with laravel/*
I'm using illuminate/* as a workaround.

[kalessil]

Hey @aand18: probably ignoring 'illuminate/*' was intended. But Laravel case has been addressed and will be in the next release (ETA next week).