Added an additional test for strict types validation #2699
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Done at |
maxhelias
approved these changes
Apr 6, 2019
alanpoulain
approved these changes
Apr 6, 2019
|
Thanks @Toflar |
I tried to track it down and it looks like it has actually never failed 😄 Here's the original build: https://travis-ci.org/api-platform/core/jobs/397805821 |
|
Some context about the initial PR: Han told me that strict types weren’t working with API Platform. I was sure that they were, so he opened a PR with a failing test 😂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apparently this has been fixed in the meantime. I still added the test and fixed it (
gettype()returnsnulluppercase).