1. 28 May, 2015 2 commits
    • Fabien Potencier's avatar
      Merge branch '1.2' into 1.3 · b682c867
      Fabien Potencier authored
      * 1.2:
        Changed Doctrine page to use utf8mb4 as sample
      b682c867
    • Fabien Potencier's avatar
      minor #1168 Changed Doctrine page to use utf8mb4 as sample (DHager) · e46e475d
      Fabien Potencier authored
      This PR was merged into the 1.2 branch.
      
      Discussion
      ----------
      
      Changed Doctrine page to use utf8mb4 as sample
      
      MySQL's `utf8` character set is a little broken, and does not cover 4-byte UTF-8 characters. In most cases it will quietly truncate the string whenever it sees one, saving incomplete text data.
      
      In  5.5.3 they introduced `utf8mb4` to fix this inconsistency, and given that it's been 5 years, it's probably safe to encourage people to use it. If their MySQL installation is older, it should be easy for them to find the distinctive string and change it back to `utf8`, and for a new project.
      
      Additional details can be found in the equivalent [pull-request for Symfony-2](https://github.com/symfony/symfony-docs/pull/5100).
      
      Commits
      -------
      
      a20f8f6a Changed Doctrine page to use utf8mb4 as sample
      e46e475d
  2. 14 May, 2015 2 commits
  3. 11 May, 2015 1 commit
  4. 08 May, 2015 10 commits
  5. 06 May, 2015 1 commit
  6. 05 May, 2015 16 commits
  7. 04 May, 2015 1 commit
    • Darien's avatar
      Changed Doctrine page to use utf8mb4 as sample · a20f8f6a
      Darien authored
      MySQL's `utf8` character set is a little broken, and does not cover 4-byte UTF-8 characters. In most cases it will quietly truncate the string whenever it sees one, saving incomplete text data.  
      
      In  5.5.3 they introduced `utf8mb4` to fix this inconsistency, and given that it's been 5 years, it's probably safe to encourage people to use it. If their MySQL installation is old, it should be easy for them to find the distinctive string and change it back to `utf8`.
      a20f8f6a
  8. 03 May, 2015 3 commits
  9. 01 May, 2015 4 commits
    • Fabien Potencier's avatar
      minor #1159 Have `Controller::generateRouteName()` always put the method first. (LawnGnome) · 938a3e9c
      Fabien Potencier authored
      This PR was merged into the 1.3 branch.
      
      Discussion
      ----------
      
      Have `Controller::generateRouteName()` always put the method first.
      
      (As requested, this is #1154 rebased against 1.3.)
      
      At present, mounted controllers can get weird route names. For instance, let's say you have this controller definition:
      
          $otherController = $app['controllers_factory'];
          $otherController->get('/{name}', function (Request $request, $name) use ($app) {
            return new Response("Goodbye $name!\n", 200, ['Content-Type' => 'text/plain']);
            });
          $app->mount('/goodbye', $otherController);
      
      The generated route name in this case will be `_goodbyeGET_name`, which technically contains everything, but is ugly.
      
      With this PR, the route name will change to `GET_goodbye_name`, which is considerably easier to parse when debugging.
      
      Commits
      -------
      
      f8d6484c Have `Controller::generateRouteName()` always put the method first.
      938a3e9c
    • Adam Harvey's avatar
      Have `Controller::generateRouteName()` always put the method first. · f8d6484c
      Adam Harvey authored
      At present, mounted controllers can get weird route names. For instance, let's
      say you have this controller definition:
      
          $otherController = $app['controllers_factory'];
          $otherController->get('/{name}', function (Request $request, $name) use ($app) {
            return new Response("Goodbye $name!\n", 200, ['Content-Type' => 'text/plain']);
            });
          $app->mount('/goodbye', $otherController);
      
      The generated route name in this case will be `_goodbyeGET_name`, which
      technically contains everything, but is ugly.
      
      With this PR, the route name will change to `GET_goodbye_name`, which is
      considerably easier to parse when debugging.
      f8d6484c
    • Fabien Potencier's avatar
      Merge branch '1.2' into 1.3 · 909c3464
      Fabien Potencier authored
      * 1.2:
        Fix return of renderView to string
        Add mention of patch method to usage docs
      
      Conflicts:
      	doc/usage.rst
      909c3464
    • Fabien Potencier's avatar
      minor #1158 Fix return of renderView to string (bburnichon) · 67e4a0f6
      Fabien Potencier authored
      This PR was merged into the 1.2 branch.
      
      Discussion
      ----------
      
      Fix return of renderView to string
      
      Commits
      -------
      
      988753a4 Fix return of renderView to string
      67e4a0f6