Skip to content

Latest commit

 

History

History
96 lines (70 loc) · 4.1 KB

Pretty_printing.markdown

File metadata and controls

96 lines (70 loc) · 4.1 KB
Raw

Pretty printing

Pretty printing is the process of converting a syntax tree back to PHP code. In its basic mode of operation the pretty printer provided by this library will print the AST using a certain predefined code style and will discard (nearly) all formatting of the original code. Because programmers tend to be rather picky about their code formatting, this mode of operation is not very suitable for refactoring code, but can be used for automatically generated code, which is usually only read for debugging purposes.

Basic usage

$stmts = $parser->parse($code);

// MODIFY $stmts here

$prettyPrinter = new PhpParser\PrettyPrinter\Standard;
$newCode = $prettyPrinter->prettyPrintFile($stmts);

The pretty printer has three basic printing methods: prettyPrint(), prettyPrintFile() and prettyPrintExpr(). The one that is most commonly useful is prettyPrintFile(), which takes an array of statements and produces a full PHP file, including opening <?php.

prettyPrint() also takes a statement array, but produces code which is valid inside an already open <?php context. Lastly, prettyPrintExpr() takes an Expr node and prints only a single expression.

Customizing the formatting

Apart from an shortArraySyntax option, the default pretty printer does not provide any functionality to customize the formatting of the generated code. The pretty printer does respect a number of kind attributes used by some notes (e.g., whether an integer should be printed as decimal, hexadecimal, etc), but there are no options to control brace placement or similar.

If you want to make minor changes to the formatting, the easiest way is to extend the pretty printer and override the methods responsible for the node types you are interested in.

If you want to have more fine-grained formatting control, the recommended method is to combine the default pretty printer with an existing library for code reformatting, such as PHP-CS-Fixer.

Formatting-preserving pretty printing

Note: This functionality is experimental and not yet complete.

For automated code refactoring, migration and similar, you will usually only want to modify a small portion of the code and leave the remainder alone. The basic pretty printer is not suitable for this, because it will also reformat parts of the code which have not been modified.

Since PHP-Parser 4.0, an experimental formatting-preserving pretty-printing mode is available, which attempts to preserve the formatting of code (those AST nodes that have not changed) and only reformat code which has been modified or newly inserted.

Use of the formatting-preservation functionality requires some additional preparatory steps:

use PhpParser\{Lexer, NodeTraverser, NodeVisitor, Parser, PrettyPrinter};

$lexer = new Lexer\Emulative([
    'usedAttributes' => [
        'comments',
        'startLine', 'endLine',
        'startTokenPos', 'endTokenPos',
    ],
]);
$parser = new Parser\Php7($lexer);

$traverser = new NodeTraverser();
$traverser->addVisitor(new NodeVisitor\CloningVisitor());

$printer = new PrettyPrinter\Standard();

$oldStmts = $parser->parse($code);
$oldTokens = $lexer->getTokens();

$newStmts = $traverser->traverse($oldStmts);

// MODIFY $newStmts HERE

$newCode = $printer->printFormatPreserving($newStmts, $oldStmts, $oldTokens);

If you make use of the name resolution functionality, you will likely want to disable the replaceNodes option. This will add resolved names as attributes, instead of directlying modifying the AST and causing spurious changes to the pretty printed code. For more information, see the name resolution documentation.

This functionality is experimental and not yet fully implemented. It should not provide incorrect code, but it may sometimes reformat more code than necessary. Open issues are tracked in issue #344. If you encounter problems while using this functionality, please open an issue, so we know what to prioritize.