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
F15625828: D13534.id32714.diff
Sun, May 18, 11:25 AM
Unknown Object (File)
Thu, May 8, 2:16 AM
Unknown Object (File)
Wed, May 7, 7:56 PM
Unknown Object (File)
Tue, May 6, 8:12 PM
Unknown Object (File)
Mon, May 5, 7:58 PM
Unknown Object (File)
Fri, Apr 25, 12:03 AM
Unknown Object (File)
Wed, Apr 23, 4:41 PM
Unknown Object (File)
Wed, Apr 23, 9:18 AM
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
Tests Skipped
Build Status
Buildable 7620
Build 8281: [Placeholder Plan] Wait for 30 Seconds
Build 8279: 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
29

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.