Skip to content

Conversation

@MarkRedeman
Copy link
Contributor

Using an empty namespace prefix is bad for performance, see composer validate --strict.

Using an empty namespace prefix is bad for performance, see `composer validate --strict`
wtfzdotnet added a commit that referenced this pull request Dec 22, 2015
Use TMDB namespace prefix in psr-4 autolaoder
@wtfzdotnet wtfzdotnet merged commit acdd114 into php-tmdb:2.0 Dec 22, 2015
@wtfzdotnet
Copy link
Member

👍 absolutely right :-), I just did a check on that composer validate --strict command but for me it just outputs the json file is valid but has a few warnings ( however it doesn't show any? ).

@MarkRedeman MarkRedeman deleted the psr-4-namespace branch December 22, 2015 22:09
@MarkRedeman
Copy link
Contributor Author

That's strange. For me it showed,

./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
Defining autoload.psr-4 with an empty namespace prefix is a bad idea for performance

Btw you can also use composer validate --strict -A, which will validate all your dependencies (which is how I initially saw the psr warning :)).

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