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

Pull master from squizlabs #1

Merged
merged 1,103 commits into from
Sep 17, 2015
Merged

Pull master from squizlabs #1

merged 1,103 commits into from
Sep 17, 2015

Conversation

scato
Copy link
Owner

@scato scato commented Sep 17, 2015

No description provided.

…nstead of always using padding to fill the space
…stead of always using padding to fill the space
gsherwood and others added 28 commits July 23, 2015 10:47
This fixes a bug in the `Squiz.Functions.FunctionDeclarationSpacing`
sniff when the `requiredSpacesAfterOpen` option was set to anything
other than 0.

When the first argument in a multiline function declaration had a
type-hint, this error would be given:

> Expected 1 spaces between opening bracket and type hint "array"; 0
found

I don’t think this check was ever intended to affect multiline
functions. The logic was such that it never does when
`requiredSpacesAfterOpen` is 0, and because this is the default, the
bug was never noticed.
HHVM 3.5-3.6 tokenize "#!/usr/bin/php" as a non-standard T_HASHBANG
instead of PHP5's T_INLINE_HTML, so convert it to the expected
T_INLINE_HTML.
findNext() might return false, so we have to check for that.
Otherwise we overwrite our loop variable and get stuck.

Detected while playing around with the horde source tree.
Fix misspellings of 'comment'
scato added a commit that referenced this pull request Sep 17, 2015
Pull master from squizlabs
@scato scato merged commit 6979367 into scato:master Sep 17, 2015
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.