New in symfony 1.2: Small things matter (3)
Here comes the third edition of small things that might make you happy in symfony 1.2.
When you test your code with unit or functional tests, it's quite handy to know if some code has not been covered.
As of symfony 1.2, the
test:coverage task outputs the code coverage for some given
./symfony test:coverage test/unit/model/ArticleTest.php lib/model/Article.php
The first argument is a test file or a test directory. The second one is the file or directory for which you want to know the code coverage.
If you want to know which lines are not covered, simply add the
./symfony test:coverage --detailed test/unit/model/ArticleTest.php lib/model/Article.php
The event system introduced in symfony 1.1 makes the framework quite flexible. As new needs arise, new events are added:
user.change_authentication: notified when a user authentication status changes. The event takes the
authenticatedflag as an argument after the change occurred.
You can read the web debug toolbar
post to learn more about the new
The form framework is made better by the addition of several methods that simplifies its usage in the templates:
renderUsing() method renders the form using a specific formatter:
// in a template, the form will be rendered using the "list" form formatter <?php echo $form->renderUsing('list') ?>
renderHiddenFields() method returns the HTML needed to display
the hidden widgets:
<form action="<?php echo url_for('@some_route') ?>"> <?php echo $form->renderHiddenFields() ?> <ul> <?php echo $form['name']->renderRow() ?> </ul> <input type="submit" /> </form>
sfForm now also implements the
<ul> <?php foreach ($form as $field): ?> <li><?php echo $field ?></li> <?php endforeach; ?> </ul>
That's all for today.
New in symfony 1.2: Small things matter (3) symfony.com/blog/new-in-symfony-1-2-small-things-matter-3Tweet this
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.