-
-
Notifications
You must be signed in to change notification settings - Fork 195
Add support for unpacking Composer packages #241
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
Conversation
About the post && unpack feature, I wonder why it's only reserved to the |
The reason is that when you require several packages at once, only some of them should be unpacked. |
Yeah, but a metapackage is precisely the kind of package that can be unpacked: if a I'm just commenting on this because |
can != should - that's the point.
Flex is only for Symfony apps yes, framework bundle is an implicit requirement of all recipes.
sure, that's the case - the false-ideas are false-ideas, only technical behavior has value here. |
Symfony Flex is currently definitely for Symfony, no questions about it. |
Based on the feedback, unpack never happens recursively. It gives more control. There is now also a new |
b243a21
to
19bafc0
Compare
45f2644
to
681745a
Compare
681745a
to
bcc3219
Compare
This PR is short but packed (pun intended) with great features.
Basically, it helps fix an issue people have with Flex: starting a new project.