Skip to content

Conversation

@klausi
Copy link
Contributor

@klausi klausi commented Feb 14, 2015

See http://php.net/manual/en/language.oop5.traits.php#language.oop5.traits.conflict

Only containing a failing test case right now, not sure where the correct place is to fix this.

@aik099
Copy link
Contributor

aik099 commented Feb 14, 2015

In other words: use traitName { doesn't increase indentation, but it should.

@gsherwood gsherwood changed the title Trait conflict resolution scope indentation Use statements don't increase the scope indent Feb 16, 2015
@gsherwood
Copy link
Member

I've fixed this issue now. Use statements were not seen as scope openers at all, but they now are.

I couldn't merge in the failing unit test because you removed the parse error (this is a special test for a previous bug fix) and the .1 and .2 files had different code in them (they only diff should be spaces vs tabs for indent). But thank you for submitting the report and failing test anyway.

@gsherwood gsherwood closed this Feb 16, 2015
@pfrenssen
Copy link
Contributor

Thanks!

jrfnl added a commit to jrfnl/PHP_CodeSniffer that referenced this pull request Jul 29, 2024
…kenizer-reorganize

Feature/tests tokenizer reorganize
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.

4 participants