-
Notifications
You must be signed in to change notification settings - Fork 34
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
Update doctrine configuration #149
Conversation
The PR looks good so far. I am not sure what you mean with the "newer way of working". |
I have updated the Readme to reflect the changes in regards to migrations. I've also added a small UPGRADE doc, documenting the changes to the migrations and ORM mapping. Please feel free to let me know if you have any more changes you'd like to see! |
Perfect. I think this would probably be tagged as 4.0 then as this is a BC break. I'm not sure if that's going to play well with other projects still using XML (and wanting to use this package). Is this possible? I'll do some testing in our Sylius project to see if it still works. |
Unfortunatly i do not currently have a project that uses XML mapping, although this should not be a problem. |
Anything else that's needs to be done? Otherwise I'd merge it and tag it as the new version. |
I'm currently using it pinned on my fork branch, and during my testing it has been working fine. Maybe a rename of the UPGRADE markdown file based on the tag you're planning to push? |
Sure, that would be great. It's planned as 4.0 |
Awesome, i've updated the readme @mamazu |
Thanks for your contribution. 🎉 |
This PR References issue #148
Note:
The overwriting of the Sylius resources has also been removed. The test application should probably be updated to reflect the newer way of working
Feedback is appreciated