Skip to content
This repository has been archived by the owner on Jan 8, 2020. It is now read-only.

CS: There MUST be one blank line after the namespace declaration. #7026

Merged
merged 1 commit into from
Dec 16, 2014

Conversation

keradus
Copy link
Contributor

@keradus keradus commented Dec 13, 2014

No description provided.

@Ocramius Ocramius added this to the 2.4.0 milestone Dec 16, 2014
@Ocramius Ocramius self-assigned this Dec 16, 2014
Ocramius added a commit that referenced this pull request Dec 16, 2014
CS: There MUST be one blank line after the namespace declaration.
@Ocramius Ocramius merged commit 6324a74 into zendframework:develop Dec 16, 2014
@Ocramius
Copy link
Member

@keradus thanks!

@keradus keradus deleted the line_after_namespace branch December 16, 2014 13:22
gianarb pushed a commit to zendframework/zend-stdlib that referenced this pull request May 15, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
gianarb pushed a commit to zendframework/zend-progressbar that referenced this pull request May 15, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
gianarb pushed a commit to zendframework/zend-cache that referenced this pull request May 15, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
gianarb pushed a commit to zendframework/zend-soap that referenced this pull request May 15, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
gianarb pushed a commit to zendframework/zend-view that referenced this pull request May 15, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
weierophinney pushed a commit to zendframework/zend-i18n-resources that referenced this pull request May 28, 2015
…_after_namespace

CS: There MUST be one blank line after the namespace declaration.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants