- 14 May, 2015 1 commit
-
-
Fabien Potencier authored
This PR was merged into the 1.3 branch. Discussion ---------- View Listener Previously #1062 and #863 TODO - [x] Documentation Commits ------- fa14af74 Remove incorrect examples and fix grammar f0d7d7c2 Basic documentation 5407435c Use PHPUnit annotation to skip test on <5.4 b4446482 Document as mixed, may be a string intended to be resolved from the CallbackResolver f2724fd2 Revert the CS fix and make a valid docComment ca9fe47b More CS fixes 4e6591c3 CS Fixes 974b49d1 Allow view listeners to be "skipped" by returning null 50150276 Restricted visibility c86b6f59 Fix docblock type a7768253 Remove callable hint for 5.3 tests 65a97117 Avoid mutating state f31bb299 Fix test 3a8e2dd5 Remove callable type hint from chain test for 5.3 a940fbe3 Clarify docblock 0bce9898 Add request to signature to test call 6bddf29e Add ViewListenerWrapper and tests 86c02016 Add view.
-
- 11 May, 2015 1 commit
-
-
Dave Marshall authored
-
- 08 May, 2015 10 commits
-
-
Fabien Potencier authored
-
Fabien Potencier authored
This PR was submitted for the master branch but it was merged into the 1.3 branch instead (closes #1122). Discussion ---------- Add OPTIONS request routing directly to Application I think it's important to add this HTTP Method directly to the application because it's often called automatically by browsers during AJAX requests. Meaning it's required that anyone sending AJAX requests to Silex will have to implement some kind of OPTIONS handling. I realize that you can use the match and method calls to do this same thing but those make routing OPTIONS requests less obvious. Commits ------- 20be5c99 Fixed whitespace issue 45dc2bcc Add options request capability to controller collection 7ca60854 Update Application add options method for handling option routing
-
jim authored
-
Jim authored
-
Jim authored
-
Fabien Potencier authored
* 1.2: updated intro docs Conflicts: doc/intro.rst
-
Fabien Potencier authored
-
Fabien Potencier authored
* 1.2: [Docs] [Providers] Fixed typo
-
Fabien Potencier authored
This PR was submitted for the master branch but it was merged into the 1.2 branch instead (closes #1162). Discussion ---------- [Docs] [Providers] Fixed typo Commits ------- cb279a24 [Docs] [Providers] Fixed typo
-
Ulf authored
-
- 06 May, 2015 1 commit
-
-
Dave Marshall authored
-
- 05 May, 2015 16 commits
-
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Dave Marshall authored
-
Beau Simensen authored
-
- 03 May, 2015 3 commits
-
-
Fabien Potencier authored
* 1.2: Phpdocs
-
Fabien Potencier authored
This PR was merged into the 1.2 branch. Discussion ---------- PHPDocs cleans ups And some tabs versus spaces. Commits ------- bd9f72eb Phpdocs
-
Possum authored
-
- 01 May, 2015 4 commits
-
-
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.
-
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.
-
Fabien Potencier authored
* 1.2: Fix return of renderView to string Add mention of patch method to usage docs Conflicts: doc/usage.rst
-
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
-
- 30 Apr, 2015 1 commit
-
-
Benoît Burnichon authored
-
- 18 Apr, 2015 1 commit
-
-
Fabien Potencier authored
This PR was merged into the 1.3 branch. Discussion ---------- updated docs for 1.3 Commits ------- 58c91cdd updated docs for 1.3
-
- 16 Apr, 2015 1 commit
-
-
Fabien Potencier authored
-
- 12 Apr, 2015 1 commit
-
-
Fabien Potencier authored
This PR was submitted for the master branch but it was merged into the 1.2 branch instead (closes #1144). Discussion ---------- Add mention of patch method to usage docs Commits ------- f8c6113d Add mention of patch method to usage docs
-