This PR was submitted for the master branch but it was merged into the 2.1 branch instead (closes#6884).
Commits
-------
c261760 Fixed missing class argument when throwing exception
Discussion
----------
Added missing parameter to Exception in DebugClassLoader
The DebugClassLoader was missing the $class argument to sprintf() when it tries to throw the exception, making the actual error you are getting more daunting :)
---------------------------------------------------------------------------
by stof at 2013-01-25T23:31:58Z
oops, sorry.
@fabpot this should be merged in 2.1 as you merged the change there
This PR was merged into the master branch.
Commits
-------
e3086cc [Console] added some missing information in the phpdoc (closes#6464)
Discussion
----------
[Console] added some missing information in the phpdoc (closes#6464)
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #6464
| License | MIT
| Doc PR | n/a
This PR was merged into the master branch.
Commits
-------
ed64413 removed deprecated message in FieldType
Discussion
----------
removed deprecated messages coming for internal calls
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #6407
| License | MIT
| Doc PR | n/a
It's probably not the cleanest code possible, but I don't see any other way to keep the type for BC and avoid the deprecated message when called internally.
That should fix the deprecated messages thrown by the Form and Validator components.
---------------------------------------------------------------------------
by stof at 2013-01-24T15:41:26Z
The cases where you should actually be warned about the deprecation of FieldType is when using ``field`` to create a field with the factory (which would not trigger the constructor)
---------------------------------------------------------------------------
by fabpot at 2013-01-24T15:46:23Z
@stof: what do you mean? That we can remove the `trigger_error()` call altogether?
---------------------------------------------------------------------------
by stof at 2013-01-24T15:49:31Z
Nobody will ever instantiate the FieldType directly as the framework is registering it (btw, you are missing the FrameworkBundle lazy registration here).
The constructor of a form type is not the right place to deprecate it as registering it does not mean it will be used in the app.
---------------------------------------------------------------------------
by fabpot at 2013-01-24T15:51:26Z
@stof: I've updated the PR to remove the `trigger_error` call.
This PR was merged into the master branch.
Commits
-------
749087e updated ValidatorExtension to avoid using a deprecated method
Discussion
----------
updated ValidatorExtension to avoid using a deprecated method
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
---------------------------------------------------------------------------
by stof at 2013-01-24T13:05:43Z
👍
Btw, this is needed to simply make it work against the ValidatorInterface by having the right expectation on getMetadataFactory()
This PR was merged into the master branch.
Commits
-------
8bfd7a7 Remove custom error handler for deprecations
efbff0c Change deprecated Min and Max constraint
c47f027 [Validator][Constraints] Update AllValidator using new Validator API
Discussion
----------
[Validator][Constraints] Update AllValidator using new Validator API
Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets:
License of the code: MIT
This PR was merged into the master branch.
Commits
-------
9264431 Remove custom error handler for deprecations
c80c17e Change deprecated Min constraint to Range constraint
a39fdd8 Remove getPropertyPath in the tests
ffa4c6f [Validator][Constraints] CollectionValidator
Discussion
----------
[Validator][Constraints] Update CollectionValidator using new Validator API
Bug fix: yes
Feature addition: no
Backwards compatibility break: no
Symfony2 tests pass: yes
Fixes the following tickets: #6648
License of the code: MIT
In the tests `$i = 1` is because in `validate` the first call to `$this->context` is `$this->context->getGroup();`, should I write this in a comment before each declaration?
---------------------------------------------------------------------------
by stof at 2013-01-15T21:50:41Z
You should also modify the CollectionValidator tests to use a different constraint than ``Min`` which is deprecated. Once it is done, these tests should not need to register a custom error handler catching deprecations anymore
---------------------------------------------------------------------------
by franmomu at 2013-01-15T22:33:43Z
Perfect, I'm going to do the same in #6743
This PR was merged into the master branch.
Commits
-------
2061cc0 Update src/Symfony/Component/Validator/Mapping/ClassMetadata.php
Discussion
----------
[Validator] ClassMetadata use deprecated methods
Bug fix: yes
Feature addition: no
Backwards compatibility break: maybe yes (I don't have the knowlegde)
Symfony2 tests pass: yes
Fixes the following tickets: ?
Todo: Nothing
License of the code: MIT
Documentation PR: Nothing
getValue() is deprecated since version 2.2 and will be removed in 2.3. Use getPropertyValue() instead.
ClassMetadata is still using the deprecated method, changed it to getPropertyValue to prevent a trigger error.
---------------------------------------------------------------------------
by fabpot at 2013-01-14T15:35:28Z
ping @bschussek
* 2.1:
[DependencyInjection] fixed the creation of synthetic services in ContainerBuilder
[Security] PHPDoc in SecurityEvents
Fix typos in README
Added an error message in the DebugClassLoader when using / instead of \.
KNOWN_ISSUES with php 5.3.16
[FrameworkBundle] fixed Client::doRequest that must call its parent method (closes#6737)
[Yaml] fixed ignored text when parsing an inlined mapping or sequence (closes#6786)
[Yaml] fixed#6773
[Yaml] fixed#6770
bumped Symfony version to 2.1.8-DEV
bumped Symfony version to 2.0.23-DEV
Conflicts:
src/Symfony/Bundle/FrameworkBundle/Client.php
src/Symfony/Component/HttpKernel/Kernel.php
This PR was squashed before being merged into the master branch (closes#6734).
Commits
-------
4d51ec0 Fix for hardcode (#6384) in choice widget
Discussion
----------
Fix for hardcode (#6384) in choice widget
empty_value should not be disabled if field is not required!
#6384
---------------------------------------------------------------------------
by sstok at 2013-01-15T15:51:08Z
You need to revert the file mode changes (100644 → 100755)
---------------------------------------------------------------------------
by MaksSlesarenko at 2013-01-18T16:44:42Z
fixed tests
---------------------------------------------------------------------------
by MaksSlesarenko at 2013-01-21T15:36:59Z
ping @fabpot
---------------------------------------------------------------------------
by fabpot at 2013-01-21T15:58:26Z
ping @bschussek
---------------------------------------------------------------------------
by MaksSlesarenko at 2013-01-23T11:15:37Z
ping @fabpot @bschussek
---------------------------------------------------------------------------
by Tobion at 2013-01-23T12:08:19Z
I think it's good to squash and merge.
---------------------------------------------------------------------------
by fabpot at 2013-01-23T12:16:37Z
Can you rebase and squash before I merge? Thanks.
---------------------------------------------------------------------------
by MaksSlesarenko at 2013-01-23T19:51:36Z
@fabpot done
This PR was merged into the master branch.
Commits
-------
7944860 [DIC] Move PrependExtensionInterface to the Extension namespace
Discussion
----------
[DIC] Move PrependExtensionInterface to the Extension namespace
@fabpot Please merge before 2.2 (no BC break) /cc @lsmith77
This PR was merged into the master branch.
Commits
-------
65b4112 fixed a circular reference (closes#6730)
Discussion
----------
fixed a circular reference (closes#6730)
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #6730
| License | MIT
| Doc PR | n/a
---------------------------------------------------------------------------
by stof at 2013-01-23T13:56:19Z
shoudln't this be moved to the component ? Someone using the TwigBridge, HttpKernel and the DI component outside the full stack framework (let's say Drupal maybe) would also face the circular reference issue
---------------------------------------------------------------------------
by fabpot at 2013-01-23T13:58:28Z
No, they won't as the problem is only if you are using the templating component. So, Silex or Drupal won't have the problem.
---------------------------------------------------------------------------
by stof at 2013-01-23T14:01:03Z
ah, the issue is indeed with the TwigEngine, not with the Twig_Environment service.
This PR was merged into the master branch.
Commits
-------
23f5145 renamed proxy to router_proxy
e5135f6 [HttpKernel] renamed path to _path to avoid collision
3193a90 made the proxy path configurable
ad82893 removed the need for a proxy route for rendering strategies
b9f0e17 [HttpKernel] made the Request required when using rendering strategies
Discussion
----------
Content renderer simplification
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | symfony/symfony-docs#2179
Todo:
- [x] submit a PR for documentation update
The first commit makes the Request required when dealing with rendering strategies (see the commit why this was a bad idea to make it optional in the first place).
The second commit removes the need for a proxy route and replaces it with the same system we have in the security component.
The third commit makes the proxy path configurable (default to `/_proxy`).
This PR has been triggered by a discussion on #6791.
---------------------------------------------------------------------------
by fabpot at 2013-01-22T09:49:37Z
My opinion:
* The first commit should be merged.
* For the second and third one, I don't have a strong opinion. One of the benefits that the content renderer and its strategies do not rely on the Routing component anymore.
---------------------------------------------------------------------------
by fabpot at 2013-01-22T15:22:47Z
Any comments? ping @Tobion @vicb
---------------------------------------------------------------------------
by Tobion at 2013-01-22T16:07:15Z
Shouldn't the class name be like `SubRequestRenderingStrategyInterface` because currently it does not say anything about what is rendered. `RenderingStrategyInterface` makes it look like it's for rendering a normal master request, i.e. templating.
---------------------------------------------------------------------------
by fabpot at 2013-01-22T16:19:26Z
@Tobion: This was actually the first name I had but I found it too long. It is indeed rendering a normal request, but only in the context of a master request.
---------------------------------------------------------------------------
by Tobion at 2013-01-22T16:23:25Z
I found the correct term for what this is about: http://en.wikipedia.org/wiki/Transclusion
So it should probably be like `Symfony/Component/HttpKernel/Transclusion/TransclusionInterface`
or `TransclusionStrategyInterface`.
So the term `rendering` is misleading as it does not really render the subrequest, but only prints a reference to the subrequest. The rendering is done by ESI processor or hinclude etc.
---------------------------------------------------------------------------
by fabpot at 2013-01-22T16:37:00Z
The `RenderingStrategyInterface` does render a request and returns a Response. One of the strategy consist of returning an ESI tag, but this is still a Response.
I don't like introducing the `Transclusion` word as (at least for me) it does not evoke anything.
---------------------------------------------------------------------------
by Tobion at 2013-01-22T16:46:10Z
Also `DefaultRenderingStrategy` is not saying anything. What is default? It should express that it directly includes the resource in the other (term `integrate` comes to my mind).
---------------------------------------------------------------------------
by kriswallsmith at 2013-01-22T17:23:21Z
How about `InlineRenderingStrategy`?
---------------------------------------------------------------------------
by vicb at 2013-01-22T17:25:17Z
@Tobion @kriswallsmith 👍
---------------------------------------------------------------------------
by kriswallsmith at 2013-01-22T17:26:17Z
Also, `SubRequestStrategyInterface` may be more apparent (`InlineSubRequestStrategy`, `EsiSubRequestStrategy`…)
---------------------------------------------------------------------------
by Tobion at 2013-01-22T18:10:19Z
`SubRequestStrategyInterface` is missing the verb somehow. A strategy for what? @kriswallsmith as an English native speaker, is transclusion also not convenient for you?
---------------------------------------------------------------------------
by fabpot at 2013-01-22T18:11:41Z
Thanks for all your suggestions, I appreciate them, but what about the whole approach? Do you agree that it is better than the current one? I'd like to avoid the bikeshedding if the approach is not better.
---------------------------------------------------------------------------
by kriswallsmith at 2013-01-22T18:22:47Z
👍 for removing the router dependency.
@Tobion perhaps request is the verb there?
---------------------------------------------------------------------------
by Tobion at 2013-01-22T19:51:20Z
I'm also fine with making it independent from the routing component because routing is about making routes configurable with placeholders etc. for nice URLs. But this is not needed for a proxy feature.
---------------------------------------------------------------------------
by kriswallsmith at 2013-01-22T20:13:48Z
@fabpot Do you anticipate ever wanting a sub request to be handled differently based on HTTP method? Just thinking of possible reasons to continue using the routing component here…
---------------------------------------------------------------------------
by fabpot at 2013-01-22T20:40:06Z
No, sub-requests only make sense for GET requests. In fact, we even enforce that in HttpContentRenderer.
---------------------------------------------------------------------------
by fabpot at 2013-01-23T06:51:54Z
I'm not going to discuss names further in the context of this PR as it has already been discussed in the initial PR that introduced these classes and because this PR does not change anything to the meaning of these classes. If you think the names can be better, feel free to open a ticket and discuss names there.
---------------------------------------------------------------------------
by vicb at 2013-01-23T07:48:36Z
If I understand correctly, both hsi and esi will generate path starting with "/_proxy", isn't it a problem wrt access_control ? should it be possible to configure a per strategy path ?
---------------------------------------------------------------------------
by fabpot at 2013-01-23T07:56:11Z
@vicb: Yes, all strategies use the `/_proxy` path when the developer uses a controller reference. But the router proxy takes care of securing the route, so there is no need to do it yourself.
---------------------------------------------------------------------------
by vicb at 2013-01-23T08:07:36Z
@fabpot that's smart, I've missed it.
Some questions though (they should be answered by UT I think - and might already have been, I have not checked)
- Isn't there a pb with urlencoding in the listener ?
- Would the listener work with fragments (`#...') ?
---------------------------------------------------------------------------
by vicb at 2013-01-23T08:31:37Z
Some more points:
- Should we validate that the router_proxy is enabled when esi are enabled (early failure ?)
- Should we be able to enable each strategy individually (ie no need to expose the signer when hsi are not used)
---------------------------------------------------------------------------
by fabpot at 2013-01-23T09:58:45Z
Enabling the router proxy when using ESI si not required. The router proxy is "only" required when you use the `controller` Twig function (or the equivalent in PHP -> `ControllerReference`). But we can probably throw an exception in the `ControllerReference` constructor if the proxy is not enabled.
Enabling each strategy individually is indeed a good idea (and that's more a general question as we could do the same for the translator loaders, or the service container loaders). Let's create another issue on this global topic.
---------------------------------------------------------------------------
by vicb at 2013-01-23T10:10:29Z
> But we can probably throw an exception in the ControllerReference constructor if the proxy is not enabled.
It should probably be in a wrapper class then ?
---------------------------------------------------------------------------
by fabpot at 2013-01-23T12:45:36Z
The listener does not need to work with fragments as URLs as they are never part of the generated URL.
The previous code allowed to pass null as a Request but that does not
really make sense as rendering a sub-request can only happen from a
master request. This was done to ease testing but that was a mistake.
This PR was merged into the master branch.
Commits
-------
731cd49 made twig extension service private
Discussion
----------
[TwigBundle] made extension a private service
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | ~
| License | MIT
| Doc PR | ~
This PR was merged into the master branch.
Commits
-------
cdf1d72 [FrameworkBundle] fixed requirement of the _controller palceholder for the proxy route (closes#6783)
Discussion
----------
[FrameworkBundle] fixed requirement of the _controller palceholder for the proxy route (closes#6783)
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #6783
| License | MIT
| Doc PR | n/a
---------------------------------------------------------------------------
by vicb at 2013-01-18T10:23:06Z
What about a UT ?
---------------------------------------------------------------------------
by vicb at 2013-01-18T11:28:41Z
and the syntax is wrong also !
---------------------------------------------------------------------------
by gimler at 2013-01-21T19:59:57Z
same problem the sonata admin bundle use
```
{% render 'sonata.admin.controller.admin:getShortObjectDescriptionAction' %}
```
rewrite to
```
{% render controller('sonata.admin.controller.admin:getShortObjectDescriptionAction') %}
```
throws
```
An exception has been thrown during the rendering of a template ("Parameter "_controller" for route "_proxy" must match "[^/\.]++" ("sonata.admin.controller.admin:getShortObjectDescriptionAction" given) to generate a corresponding URL.") in "SonataAdminBundle:CRUD:edit.html.twig".
```
with the requirement fix it throws
```
An exception has been thrown during the rendering of a template ("Unable to parse the controller name "sonata".") in "SonataAdminBundle:CRUD:edit.html.twig".
```
---------------------------------------------------------------------------
by fabpot at 2013-01-22T06:40:14Z
ok, I've updated the patch. There is now a static segment (`/for`) between the controller and the format, which should fix the problem.
While thinking about this, there is another option, which might be even better: removing the need for the proxy route altogether and check for a defined path like `/_proxy`. It would remove the dependency on a Url Generator in the rendering strategy, and would not make the router proxy listener any more complex.
---------------------------------------------------------------------------
by gimler at 2013-01-22T07:20:43Z
+1 for me the patch works i will open a PR for sonata doctrine orm bundle
```
{% render controller('sonata.admin.controller.admin:getShortObjectDescriptionAction', {}, {
'code': sonata_admin.field_description.associationadmin.code,
'objectId': sonata_admin.field_description.associationadmin.id(sonata_admin.value),
'uniqid': sonata_admin.field_description.associationadmin.uniqid
})
```
---------------------------------------------------------------------------
by gimler at 2013-01-22T07:22:21Z
When the proxy route is nessesary we should add a note into the upgrade guide.
+1 for less complexesy
---------------------------------------------------------------------------
by fabpot at 2013-01-22T08:02:12Z
There is one issue with removing the proxy route: when generating a proxy URL, we need a Request instance, which is not always the case. I'm going to submit another PR to "fix" that first.
---------------------------------------------------------------------------
by vicb at 2013-01-22T08:17:51Z
> It would remove the dependency
Paul leaves this body :)
---------------------------------------------------------------------------
by Tobion at 2013-01-22T08:53:52Z
I don't think removing the proxy route is good. That's the purpose of the routing system to handle generating and matching. Now if you do it manually it will probably show a bad approach to people to handle such stuff.
Also people cannot see what routes are defined explicitly and use tools like `router:debug`.
---------------------------------------------------------------------------
by fabpot at 2013-01-22T09:28:55Z
@Tobion: see #6829
---------------------------------------------------------------------------
by fabpot at 2013-01-22T09:57:57Z
I've again changed the route pattern to avoid any possible problems (even if a controller contains a `/`).
---------------------------------------------------------------------------
by Tobion at 2013-01-22T10:16:03Z
Can a controller contain `/`? It's neither a valid service nor a valid class name or?
---------------------------------------------------------------------------
by mvrhov at 2013-01-22T10:40:26Z
AFAIK yes, at least I used Namespace/SubController more then once...
* 2.0:
[DependencyInjection] fixed the creation of synthetic services in ContainerBuilder
[Security] PHPDoc in SecurityEvents
[FrameworkBundle] fixed Client::doRequest that must call its parent method (closes#6737)
[Yaml] fixed ignored text when parsing an inlined mapping or sequence (closes#6786)
[Yaml] fixed#6773
[Yaml] fixed#6770
bumped Symfony version to 2.0.23-DEV
Conflicts:
src/Symfony/Component/DependencyInjection/ContainerBuilder.php
src/Symfony/Component/HttpKernel/Kernel.php
src/Symfony/Component/Yaml/Inline.php
src/Symfony/Component/Yaml/Tests/InlineTest.php
This PR was merged into the 2.0 branch.
Commits
-------
4119caf [DependencyInjection] fixed the creation of synthetic services in ContainerBuilder
Discussion
----------
[DependencyInjection] fixed the creation of synthetic services in ContainerBuilder
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
---------------------------------------------------------------------------
by stof at 2013-01-22T00:14:29Z
👍
This PR was merged into the master branch.
Commits
-------
94f6116 renamed hostname to host in the routing system (closes#6775)
001734a [Validator] fixed phpdoc
18b9e68 [HttpFoundation] renamed hostname to host in the test to be consistent
Discussion
----------
Hostname rename to host
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no (does not exist in 2.1)
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #6775
| License | MIT
| Doc PR | symfony/symfony-docs#2165
see #6775
---------------------------------------------------------------------------
by WouterJ at 2013-01-21T18:44:20Z
+1
As explained in #6775, this has been done for the following reasons:
1. It's also Request::getHost()
2. The term hostname has been obsoleted in
http://tools.ietf.org/html/rfc3986#appendix-D.2 and uses the host only
3. hostname in the RFC was defined as the registered domain name, but we
probably also want to match IP-Adresses with the pattern which is the
host = IP-literal / IPv4address / reg-name for.
This PR was squashed before being merged into the 2.0 branch (closes#6818).
Commits
-------
598ae9d [Security] PHPDoc in SecurityEvents
Discussion
----------
[Security] PHPDoc in SecurityEvents
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
I'm not sure about the description given.
