Page MenuHomePhabricator

Add a linter rule for newlines after PHP open tags
ClosedPublic

Authored by joshuaspence on Jul 2 2015, 9:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Dec 21, 3:46 PM
Unknown Object (File)
Mon, Dec 16, 3:09 PM
Unknown Object (File)
Sun, Dec 15, 5:49 PM
Unknown Object (File)
Sat, Dec 14, 3:03 PM
Unknown Object (File)
Fri, Dec 6, 4:17 AM
Unknown Object (File)
Thu, Dec 5, 3:37 AM
Unknown Object (File)
Tue, Dec 3, 5:09 AM
Unknown Object (File)
Thu, Nov 28, 1:43 PM
Subscribers

Details

Summary

<?php\n\n... is much easier to read than <?php\n.... Depends on D13889 and D13890.

Test Plan

Added unit tests.

Diff Detail

Repository
rARC Arcanist
Branch
master
Lint
Lint Passed
Unit
Test Failures
Build Status
Buildable 7122
Build 7296: [Placeholder Plan] Wait for 30 Seconds
Build 7295: arc lint + arc unit

Event Timeline

joshuaspence retitled this revision from to Add a linter rule for newlines after PHP open tags.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
src/lint/linter/xhpast/rules/ArcanistNewlineAfterOpenTagXHPASTLinterRule.php
28

I think this phrasing is maybe a little ambiguous, since it doesn't mean "a single newline character", but could be interpreted like that (i.e. "<?php\n1+1" has "a single newline character", but is not desired). Maybe "an empty line"?

This revision is now accepted and ready to land.Jul 2 2015, 9:48 PM

The fact that I needed to modify so many lint-test files was motivation for D14010.

This revision was automatically updated to reflect the committed changes.