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

Comply with CakePHP Codinging Standards #60

Merged
merged 1 commit into from
Nov 18, 2014
Merged

Comply with CakePHP Codinging Standards #60

merged 1 commit into from
Nov 18, 2014

Conversation

Indemnity83
Copy link
Contributor

There are some minor deviations from the CakePHP Coding Standards that I end up fixing each time I clone the project, to get the CakePHP Code Sniffer to pass successfully. I figured they should probably just be made to the master.

One note though; the three standard php files under app/Config/Schema also cause the sniffer to throw warnings due to missing documentation blocks but this isn't special to the app-template repo, its how CakePHP ships so I wasn't certain how to handle these three files (I usually delete them shortly after cloning).

If it is desired to have a 100% pass right after cloning, I'm more than happy to add some documentation to the files and submit a new pull request.

ADmad added a commit that referenced this pull request Nov 18, 2014
…s-compliance

Comply with CakePHP Codinging Standards
@ADmad ADmad merged commit 69f700e into FriendsOfCake:master Nov 18, 2014
@Indemnity83 Indemnity83 deleted the feature/cakephp-code-standards-compliance branch November 18, 2014 19:20
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.

2 participants