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
It's a little bit confusing:
in the http://symfony.com/doc/download-best-practices-book/ at the 7th page there's:
" will contain a fresh new project based on the most recent stable Symfony version available."
and a snippet showing output with 2.6 version installed after composer create-project run,
but symfony 2.5.6 installed intead.
I assume 2.6 not stable yet, or not long term support, but book and real-life a little differs :)
Another one: going further, command
"php app/console generate:bundle --namespace=AppBundle --dir=src --format=annotation
--no-interaction" produce
[InvalidArgumentException]
The namespace must contain a vendor namespace (e.g. "VendorName\AppBundle"
instead of simply "AppBundle").
If you've specified a vendor namespace, did you forget to surround it with
quotes (init:bundle "Acme\BlogBundle")?
Can be confusing for newcomers, just IMHO.
The text was updated successfully, but these errors were encountered:
It's a little bit confusing:
in the http://symfony.com/doc/download-best-practices-book/ at the 7th page there's:
" will contain a fresh new project based on the most recent stable Symfony version available."
and a snippet showing output with 2.6 version installed after composer create-project run,
but symfony 2.5.6 installed intead.
I assume 2.6 not stable yet, or not long term support, but book and real-life a little differs :)
Another one: going further, command
"php app/console generate:bundle --namespace=AppBundle --dir=src --format=annotation
--no-interaction" produce
[InvalidArgumentException]
The namespace must contain a vendor namespace (e.g. "VendorName\AppBundle"
instead of simply "AppBundle").
If you've specified a vendor namespace, did you forget to surround it with
quotes (init:bundle "Acme\BlogBundle")?
Can be confusing for newcomers, just IMHO.
The text was updated successfully, but these errors were encountered: