You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description #26671 reduced clutter while looking at exceptions, however made working with internal-vendor stuff harder. In larger projects it's not uncommon to have private packages and use them in the project. It's very useful to actually see them in stack traces.
Ideal solution
When vendor part of PSR-4 namespace matches current project namespace code should be treated as belonging to the project..
Simple solution
Maybe we can add configurable whitelist for vendors based on vendor/[directory] which should be ignored while deciding on the code being vendor vs. non-vendor?
Description
#26671 reduced clutter while looking at exceptions, however made working with internal-vendor stuff harder. In larger projects it's not uncommon to have private packages and use them in the project. It's very useful to actually see them in stack traces.
Ideal solution
When vendor part of PSR-4 namespace matches current project namespace code should be treated as belonging to the project..
Simple solution
Maybe we can add configurable whitelist for vendors based on
vendor/[directory]
which should be ignored while deciding on the code being vendor vs. non-vendor?ping @javiereguiluz
The text was updated successfully, but these errors were encountered: