Skip to content
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

Arraycollection matching method multiple ordering fix #64

Merged
merged 2 commits into from
Sep 11, 2015
Merged

Arraycollection matching method multiple ordering fix #64

merged 2 commits into from
Sep 11, 2015

Conversation

baileylo
Copy link
Contributor

@baileylo baileylo commented Aug 4, 2015

This is a copy of #59 that includes unit tests.

array('foo' => 2, 'bar' => 3)
));

$expected = [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not compatible with PHP 5.3, which is still supported

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, missed that short array syntax.

@baileylo
Copy link
Contributor Author

baileylo commented Aug 4, 2015

@stof Fixed php 5.3 support issues(array short syntax).

@stof
Copy link
Member

stof commented Aug 4, 2015

👍

@stof
Copy link
Member

stof commented Aug 4, 2015

@Ocramius it would be great to merge this bugfix and to release 1.3.1

@delasallejean
Copy link

@baileylo thanks !
Closing #59

@baileylo
Copy link
Contributor Author

@stof Do you know where we are with merging this?

@fsevestre
Copy link

@stof Any news about this PR ?

deeky666 added a commit that referenced this pull request Sep 11, 2015
…multiple-ordering-fix

Arraycollection matching method multiple ordering fix
@deeky666 deeky666 merged commit 866e100 into doctrine:master Sep 11, 2015
@deeky666
Copy link
Member

Thanks! Tagging is up to @Ocramius though.

@respinoza
Copy link

@Ocramius Any news on tagging a new release including this fix?

Thank you.

@zBart
Copy link

zBart commented Dec 31, 2015

Also having this issue
@Ocramius: a 1.3.1 update would be great!

@sdufel
Copy link

sdufel commented Jan 27, 2016

@Ocramius : +1 for a 1.3.1

@respinoza
Copy link

@Ocramius @deeky666 Would be possible to tag a new release ? (1.3.1)
Thank you!

@jakeasmith
Copy link

Sooo... how 'bout that 1.3.1? Or is this project no longer maintained?

@guilhermeblanco
Copy link
Member

We should tag a 1.4 version soon... =)
Just need to review/merge other non-BC breaking features... demands some time to carefully review and accept them. My current focus is setting the path for ORM v3, but I'm sure other contributors can handle that in a reasonable timeframe.

@Ocramius
Copy link
Member

Ocramius commented Jun 1, 2016

Likely going to work on these repos after DPC, which is at the end of the month.

@trickeyone
Copy link
Contributor

Could we maybe get a new release including this?

@mikeSimonson
Copy link
Contributor

@trickeyone Done

@deeky666
Copy link
Member

deeky666 commented Feb 1, 2017

@mikeSimonson what am I supposed to do here?

@mikeSimonson
Copy link
Contributor

mikeSimonson commented Feb 1, 2017

@deeky666 nothing, but you merge the PR so it was assigned to you. I taught that it was the new ™️ policy

@Ocramius Ocramius added the Bug label Feb 1, 2017
@Ocramius Ocramius added this to the 1.5 milestone Feb 1, 2017
@deeky666
Copy link
Member

deeky666 commented Feb 1, 2017

@mikeSimonson you are right I did indeed :D Didn't remember. Thanks.

@mikeSimonson mikeSimonson added this to the 1.4.0 milestone Feb 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.