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

Add strict type checking for array_search() and array_keys(). #624

Merged
merged 1 commit into from
Jul 25, 2016

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Jul 19, 2016

Will only check for the $strict parameter for array_keys() if the second parameter has been set.

Fixes #503.

The file/sniff name is now a bit dated as the sniff checks for more than just in_array(), but changing the file/sniff/classname would break backward compatibility.

What do you think ?

Will only check for the `$strict` parameter for `array_keys()` if the second parameter has been set.

Fixes #503.

The file/sniff name is now a bit dated as the sniff checks for more than just `in_array()`, but changing the file/sniff/classname would break backward compatibility.

What do you think ?
@JDGrimes JDGrimes added this to the 0.10.0 milestone Jul 25, 2016
@JDGrimes JDGrimes merged commit c3cb7c7 into develop Jul 25, 2016
@JDGrimes JDGrimes deleted the WPCS/feature/issue-503-more-strict-array-checks branch July 25, 2016 21:21
@JDGrimes
Copy link
Contributor

The file/sniff name is now a bit dated as the sniff checks for more than just in_array(), but changing the file/sniff/classname would break backward compatibility.

What do you think ?

Yeah, we'll just leave it like it is.

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