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

Explicit casting of first and max results #26

Merged
merged 5 commits into from
Apr 14, 2015
Merged

Conversation

Ocramius
Copy link
Member

@Ocramius Ocramius commented May 7, 2014

Just a suggestion - will add tests for it later if this is actually wanted behavior

Ping @EvanDotPro

@EvanDotPro
Copy link

👍

@Ocramius
Copy link
Member Author

Ocramius commented May 7, 2014

Note that this introduces a minor breakage in my opinion: now the return value of getSortings is always array, even when no sortings were given.

This simplifies consumer apps, but could potentially break apps that did a null check against the sortings to determine if there are any.

guilhermeblanco added a commit that referenced this pull request Apr 14, 2015
Explicit casting of first and max results
@guilhermeblanco guilhermeblanco merged commit 539cf62 into master Apr 14, 2015
@guilhermeblanco guilhermeblanco deleted the hotfix/type-hints branch April 14, 2015 21:36
@Ocramius Ocramius added this to the 1.3 milestone Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants