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

Returned an array when fetching all values when there is no result. #1489

Merged
merged 1 commit into from
Mar 2, 2020

Conversation

Daniel-KM
Copy link
Contributor

This is more logic and avoids to check the result when all values are wanted (can be used directly by foreach without setting default).

@zerocrates
Copy link
Member

This can probably go into a version 3 without issue... otherwise I'd be slightly concerned about the backwards incompatibility.

@Daniel-KM
Copy link
Contributor Author

All pull requests I sent are on my dev server, a demo server. They works fine with all my modules and other ones that I use. I didn't check other modules. For this commit, generally the check is ! or empty(), so there is no issue.

@zerocrates zerocrates merged commit 7677b0e into omeka:develop Mar 2, 2020
@Daniel-KM Daniel-KM deleted the feature/return_value branch March 3, 2020 09:15
Daniel-KM pushed a commit to Daniel-KM/Omeka-S that referenced this pull request Mar 9, 2020
Returned an array when fetching all values when there is no result.
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