Skip to content

Conversation

@sampart
Copy link
Collaborator

@sampart sampart commented Aug 4, 2017

The idea here is to get to a place where composer install runs and the project's tests run successfully. I'm not sure that the composer approach I've taken (768d12f) is the right one, but it's one option. Some tests have been fixed in 1b53192, but there are still many more which error (run php tests.php to see).

Once this PR has been finished, the plan is to build on it to make the bundle fully compatible with Symfony 2.8 (no deprecated calls).

Sam Partington added 2 commits August 1, 2017 16:09
You can't just do `composer update` here - that'll try and bring Symfony all the way up to 2.8, which this package isn't ready for!
Given that, I ran `composer update --prefer-lowest`.  The intention is to update the lock file further in future with newer versions, but this works for now.

I did temporarily lock doctrine/common on its original version to avoid that being downgraded for no reason.
I added the following to composer.json before running the update, but didn't need to leave it in, since this version-lock is already in the lock file:
"doctrine/common": "2.3.x-dev#bb0aebb"
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