This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes#13334).
Discussion
----------
[Yaml] Fixed#10597: Improved Yaml directive parsing
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #10597
| License | MIT
| Doc PR | N/A
There was a problem with the regular expression used to process the YAML directive. The modifier `s` made the regex too greedy, replacing everything but the last line of the YAML. Existing tests using the YAML directive contained only one line, that's why they were passing.
Commits
-------
95d8ce3 [Yaml] Fixed#10597: Improved Yaml directive parsing
This PR was merged into the 2.6 branch.
Discussion
----------
[Form] Fixed check of violation constraint #12792
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #12792
| License | MIT
| Doc PR |
ConstraintViolation::getConstraint() must not expect to provide a constraint as long as Symfony\Component\Validator\ExecutionContext exists (before 3.0)
Commits
-------
aedabc7 [Form] Fixed check of violation constraint #12792
This PR was merged into the 2.7 branch.
Discussion
----------
fixed deprecation summary and missing error_reporting() in tests
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
367184a fixed deprecation summary and missing error_reporting() in tests
ConstraintViolation::getConstraint() must not expect to provide a
constraint as long as Symfony\Component\Validator\ExecutionContext
exists (before 3.0)
This PR was merged into the 2.7 branch.
Discussion
----------
[FrameworkBundle] avoid using deprecated classes for reflection
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
26fa1a5 [FrameworkBundle] avoid using deprecated classes for reflection
This PR was merged into the 2.7 branch.
Discussion
----------
Make that AddExpressionLanguageProviderPass works with aliases
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #12847
| License | MIT
| Doc PR |
Replaces #12982 by @maarekj (includes his commit).
Commits
-------
16a22cd [FrameworkBundle] Add a test case for service aliases used with AddExpressionLanguageProviderPass.
fd97cef [FrameworkBundle] fixed#12847 AddExpressionLanguageProviderPass
This PR was merged into the 2.7 branch.
Discussion
----------
[Security] removed usage of the deprecated SecurityContextInterface
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
This PR removed internal usage of SecurityContextInterface in favor of the new alternatives, it also fixes removes as many deprecation notices as possible for the Security component.
Commits
-------
ba71b68 added type-hint
91d01d8 [Security] removed usage of the deprecated SecurityContextInterface
This PR was merged into the 2.7 branch.
Discussion
----------
[Form] fixed deprecation triggers, removed usage of deprecated features
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
60bc402 [Form] fixed deprecation triggers, removed usage of deprecated features
This PR was merged into the 2.7 branch.
Discussion
----------
[EventDispatcher] fixed deprecation notices in the EventDispatcher Component
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
98047ae [EventDispatcher] fixed deprecation notices in the EventDispatcher Component
This PR was merged into the 2.7 branch.
Discussion
----------
[Yaml] removed deprecation notices on internal constant
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | antonioribeiro/tracker#56, #13306
| License | MIT
| Doc PR | n/a
Reverting the deprecated notices on `Unescaper::ENCODING` for two reasons:
* The constant is only used internally and nobody ever used it anyway;
* The deprecation notice is ALWAYS triggered when using the YAML component.
Commits
-------
faeed58 [Yaml] removed deprecation notices on internal constant
This PR was merged into the 2.7 branch.
Discussion
----------
[HttpFoundation] maked a test as being for deprecated feature
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
a2ea28d [HttpFoundation] maked a test as being for deprecated feature
This PR was merged into the 2.7 branch.
Discussion
----------
[Yaml] maked a test as being for deprecated feature
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
651f5fb [Yaml] maked a test as being for deprecated feature
This PR was merged into the 2.5 branch.
Discussion
----------
[Security] moved test files into the right place
Commits
-------
0601ed3 [Security] moved test files into the right place
This PR was merged into the 2.7 branch.
Discussion
----------
[HttpKernel] fixed deprecation notices for ESI classes
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
Commits
-------
bd954aa [HttpKernel] fixed deprecation notices for ESI classes
This PR was merged into the 2.5 branch.
Discussion
----------
[Form] fixed the CSRF extension to allow using only the new interfaces
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
The CSRF extension did not allow to only use the new interfaces, which leads to deprecation notices you cannot get rid of in 2.7.
Commits
-------
555b010 [Form] fixed the CSRF extension to allow using only the new interfaces
This PR was merged into the 2.7 branch.
Discussion
----------
[Form] tweaked a deprecation message
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
While upgrading an app to 2.7, I found this message unclear. To be honest, and like many developers, I did not read the entire message and I missed the "cast to a string" part.
Commits
-------
a396b41 [Form] tweaked a deprecation message
This PR was merged into the 2.7 branch.
Discussion
----------
[Form] moved a deprecation notice
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | n/a
| License | MIT
| Doc PR | n/a
This deprecation notice on BindListener was wrongly put at the top of the class. This listener is always registered to provide BC, but the deprecation notice should only be generated when taking the path that is deprecated.
Commits
-------
050f4bc [Form] moved a deprecation notice