Skip to content

Conversation

@weaverryan
Copy link
Member

This could create a situation where we tell a user to install libraries
A, B & C only, but really, we also depend on library D, which was
not recommended because we are missing that dependency from our Maker.
However, library D may have been installed in the functional test
(because we previously installed ALL dependencies, even if it was
related to a class we already had).

This would have caught #256.

This could create a situation where we tell a user to install libraries
A, B & C only, but really, we also depend on library D, which was
not recommended because we are missing that dependency from our Maker.
However, library D may have been installed in the functional test
(because we previously installed ALL dependencies, even if it was
related to a class we already had).
@weaverryan weaverryan force-pushed the fix-dependencies-functional-test branch from ef9b61a to ddd3ed4 Compare September 6, 2018 14:25
Also, one test case has an optional Doctrine dep, but we need it
for the test - so, including it.
@weaverryan weaverryan force-pushed the fix-dependencies-functional-test branch from ddd3ed4 to 1c3002c Compare September 6, 2018 16:53
@weaverryan weaverryan closed this in 2250722 Sep 6, 2018
@weaverryan weaverryan deleted the fix-dependencies-functional-test branch September 6, 2018 19:39
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