Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Oct 18, 2012
  1. @webmozart
Commits on Jul 20, 2012
  1. @parhs

    Fixed buildViewBottomUp docs

    parhs authored
Commits on Jul 10, 2012
  1. @webmozart
Commits on Jul 9, 2012
  1. @fabpot
Commits on Jun 14, 2012
  1. @stof
Commits on Jun 12, 2012
  1. @fabpot
Commits on May 28, 2012
  1. @iteman

    [Form] fixed a bug that caused input date validation not to be strict…

    iteman authored
    … when using the single_text widget with a datetime field
  2. @iteman

    [Form] fixed a bug that caused input date validation not to be strict…

    iteman authored
    … when using the single_text widget with a date field
Commits on May 22, 2012
  1. @fabpot

    merged branch TonyMalz/VALIDATORT_TYPEGUESS_FIX (PR #4251)

    fabpot authored
    Commits
    -------
    
    f883953 TypeGuess fixed for Date/Time constraints
    41bed29 [Form] fixed invalid 'type' option in ValidatorTypeGuesser for Date/TimeFields
    
    Discussion
    ----------
    
    [Form] fixed invalid 'type' option in ValidatorTypeGuesser for Date/TimeFields
    
    Automatic field type guessing breaks, if you use any of the Date/Time
    constraints (i.e. Symfony\Component\Validator\Constraints\DateTime), since these field types have no 'type' option defined.
    (See getDefaultOptions() in DateTimeType.php)
    
    ---------------------------------------------------------------------------
    
    by travisbot at 2012-05-10T15:25:16Z
    
    This pull request [passes](http://travis-ci.org/symfony/symfony/builds/1296309) (merged 005bdbb0 into 68eca0f9).
    
    ---------------------------------------------------------------------------
    
    by travisbot at 2012-05-18T15:50:39Z
    
    This pull request [passes](http://travis-ci.org/symfony/symfony/builds/1367774) (merged f8839532 into a04acc89).
    
    ---------------------------------------------------------------------------
    
    by TonyMalz at 2012-05-18T15:58:57Z
    
    @bschussek Ok, changed it to 'input'
    
    ---------------------------------------------------------------------------
    
    by bschussek at 2012-05-22T08:18:27Z
    
    :+1:
Commits on May 21, 2012
  1. @fabpot

    fixed CS

    fabpot authored
Commits on May 20, 2012
  1. @fabpot

    fixed CS

    fabpot authored
Commits on May 18, 2012
  1. @fabpot

    fixed CS

    fabpot authored
  2. @TonyMalz
  3. @TonyMalz

    [Form] fixed invalid 'type' option in ValidatorTypeGuesser for Date/T…

    TonyMalz authored
    …imeFields
    
    Field type guessing breaks, if you use any of the Date/Time
    constraints, since these field types have no 'type' default option
    defined.
Commits on May 15, 2012
  1. @fabpot

    fixed phpdoc @param alignment

    fabpot authored
Commits on May 14, 2012
  1. @Romain-Geissler
Commits on Mar 16, 2012
  1. Changed instances of \DateTimeZone::UTC to 'UTC' as the constant is n…

    Drew Butler authored
    …ot valid a produces this error when DateTimeZone is instantiated: DateTimeZone::__construct() [<a href='datetimezone.--construct'>datetimezone.--construct</a>]: Unknown or bad timezone (1024)
Commits on Mar 15, 2012
  1. @xavierbriand

    Revert "Throw exception when "date_widget" option is not equal to "ti…

    xavierbriand authored
    …me_widget""
    
    This reverts commit 3c2539f.
    
    Conflicts:
    
    	tests/Symfony/Tests/Component/Form/Extension/Core/Type/DateTimeTypeTest.php
Commits on Mar 12, 2012
  1. @alan0101c
Commits on Mar 11, 2012
  1. @stof

    [Form] Moved the Validator component to the suggest section

    stof authored
    There is no hard dependency to the Validator component.
Commits on Feb 22, 2012
  1. Updated LICENSE files copyright

    marc.weistroff authored
Commits on Jan 26, 2012
  1. @manuelkiessling

    [FormType] Fixed broken MoneyType regexp for JPY

    manuelkiessling authored
    The regexp in MoneyType doesn't work if currency format has no decimal
    (like JPY) and doesn't work either if the currency symbol is unicode
    
    This change fixes both issues and adds a unit test
Commits on Jan 18, 2012
  1. @fabpot

    fixed CS

    fabpot authored
Commits on Jan 11, 2012
  1. @fabpot

    fixed some phpdoc

    fabpot authored
Commits on Jan 10, 2012
  1. @kriswallsmith
Commits on Jan 5, 2012
  1. @fabpot
Commits on Dec 18, 2011
  1. @fabpot

    fixed CS

    fabpot authored
  2. @fabpot

    tweaked the README files

    fabpot authored
  3. @fabpot

    merged branch lsmith77/component_readmes (PR #2561)

    fabpot authored
    Commits
    -------
    
    1e370d7 typo fix
    93d8d44 added some more infos about Config
    27efd59 added READMEs for the bridges
    34fc866 cosmetic tweaks
    d6af3f1 fixed README for Console
    6a72b8c added basic README files for all components
    
    Discussion
    ----------
    
    added basic README files for all components and bridges
    
    heavily based on http://fabien.potencier.org/article/49/what-is-symfony2 and the official Symfony2 documentation
    
    ---------------------------------------------------------------------------
    
    by jmikola at 2011/11/03 13:36:07 -0700
    
    Great work. For syntax highlighting on the PHP snippets, you could add "php" after the three backticks.
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/11/03 13:41:29 -0700
    
    done
    
    ---------------------------------------------------------------------------
    
    by stealth35 at 2011/11/03 13:49:31 -0700
    
    Nice job, but you also need to add `<?php`
    
    ex :
    
    ``` php
    <?php
    use Symfony\Component\DomCrawler\Crawler;
    
    $crawler = new Crawler();
    $crawler->addContent('<html><body><p>Hello World!</p></body></html>');
    
    print $crawler->filter('body > p')->text();
    ```
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/11/03 13:56:57 -0700
    
    done
    
    ---------------------------------------------------------------------------
    
    by ericclemmons at 2011/11/03 19:57:57 -0700
    
    @lsmith77 Well done!  This makes consumption of individual components that much easier, *especially* now that `composer.json` files have been added.
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/11/04 01:18:23 -0700
    
    ok .. fixed the issues you mentioned @fabpot
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/11/11 15:00:27 -0800
    
    @fabpot anything else left? seems like an easy merge .. and imho there is considerable benefit for our efforts to spread the word about the components with this PR merged.
    
    ---------------------------------------------------------------------------
    
    by drak at 2011/11/11 18:54:13 -0800
    
    You know, it might be a nice idea to put a link to the documentation for each component if there is some at symfony.com
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/11/12 00:59:14 -0800
    
    i did that in some. but i might have missed a few places.
    On 12.11.2011, at 03:54, Drak <reply@reply.github.com> wrote:
    
    > You know, it might be a nice idea to put a link to the documentation for each component if there is some at symfony.com
    >
    > ---
    > Reply to this email directly or view it on GitHub:
    > symfony/symfony#2561 (comment)
    
    ---------------------------------------------------------------------------
    
    by breerly at 2011/11/21 10:28:36 -0800
    
    Pretty excited with this.
    
    ---------------------------------------------------------------------------
    
    by dbu at 2011/11/24 00:02:50 -0800
    
    is there anything we can help with to make this ready to be merged?
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/12/18 02:39:23 -0800
    
    @fabpot: seriously .. if you are not going to deliver something "better" and don't provide a reason what is wrong with this .. then its beyond frustrating. i obviously do not claim that these README's are perfect (and certainly still no replacement for proper documentation), but I do claim that in their current form they are a radical step forward to potential users of the Symfony2 components.
Commits on Dec 15, 2011
  1. @stloyd
Commits on Dec 13, 2011
  1. @Burgov
  2. @fabpot

    [DoctrineBridge] fixed some CS

    fabpot authored
Commits on Nov 23, 2011
  1. @Seldaek
Commits on Nov 22, 2011
  1. @fabpot

    merged branch hlecorche/valid-form-w3c (PR #2676)

    fabpot authored
    Commits
    -------
    
    78e9b2f [Form] Fixed textarea_widget (W3C standards)
    
    Discussion
    ----------
    
    [Form] Fixed textarea_widget (W3C standards)
    
    Textarea widget included the "pattern" attribute but is not valid by W3C standards.
    
    (See PR 2666 - New PR because rebase inside the 2.0 branch)
    
    ---------------------------------------------------------------------------
    
    by fabpot at 2011/11/18 09:01:41 -0800
    
    @hlecorche: Thanks for your work on this issue. Can you update the unit tests to be sure that this case is covered? If you're not comfortable with this, just tell me and I will do it myself
    
    ---------------------------------------------------------------------------
    
    by hlecorche at 2011/11/19 02:51:06 -0800
    
    @fabpot: I did'nt commited because I am not sure. I changed the "tests/Symfony/Tests/Component/Form/AbstractLayoutTest.php" file :
    
        public function testTextarea()
        {
            $form = $this->factory->createNamed('textarea', 'na&me', 'foo&bar', array(
                'property_path' => 'name',
                'pattern' => 'foo',
            ));
    
            $this->assertWidgetMatchesXpath($form->createView(), array(),
        '/textarea
        [@name="na&me"]
        [not(@pattern)]
        [.="foo&bar"]
        '
            );
        }
    
    Is it correct?
  2. @fabpot
Something went wrong with that request. Please try again.