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)
Sun, Nov 24, 4:30 AM
Unknown Object (File)
Thu, Oct 31, 12:12 PM
Unknown Object (File)
Mon, Oct 28, 10:58 AM
Unknown Object (File)
Oct 22 2024, 10:34 PM
Unknown Object (File)
Oct 19 2024, 1:33 PM
Unknown Object (File)
Oct 15 2024, 8:51 AM
Unknown Object (File)
Sep 30 2024, 5:35 PM
Unknown Object (File)
Sep 24 2024, 4:15 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 Passed
Build Status
Buildable 7839
Build 8710: [Placeholder Plan] Wait for 30 Seconds
Build 8709: 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.