This PR was merged into the 2.7 branch.
Discussion
----------
[PhpUnit] new PhpUnit bridge
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #13644
| License | MIT
| Doc PR | -
From the proposed README:
PHPUnit Bridge
==============
Provides utilities for PHPUnit, especially user deprecation notices management.
It comes with the following features:
* disable the garbage collector;
* auto-register `class_exists` to load Doctrine annotations;
* print a user deprecation notices summary at the end of the test suite.
Handling user deprecation notices is sensitive to the SYMFONY_DEPRECATIONS_HELPER
environment variable. This env var configures 3 behaviors depending on its value:
* when set to `strict`, all but legacy-tagged deprecation notices will make tests
fail. This is the recommended mode for best forward compatibility.
* `weak` on the contrary will make tests ignore all deprecation notices.
This is the recommended mode for legacy projects that must use deprecated
interfaces for backward compatibility reasons.
* any other value will respect the current error reporting level.
All three modes will display a summary of deprecation notices at the end of the
test suite, split in two groups:
* **Legacy** deprecation notices denote tests that explicitly test some legacy
interfaces. In all 3 modes, deprecation notices triggered in a legacy-tagged
test do never make a test fail. There are four ways to mark a test as legacy:
- make its class start with the `Legacy` prefix;
- make its method start with `testLegacy`;
- make its data provider start with `provideLegacy` or `getLegacy`;
- add the `@group legacy` annotation to its class or method.
* **Remaining/Other** deprecation notices are all other (non-legacy)
notices, grouped by message, test class and method.
Usage
-----
Add this bridge to the `require-dev` section of your composer.json file
(not in `require`) with e.g.
`composer require --dev "symfony/phpunit-bridge"`.
When running `phpunit`, you will see a summary of deprecation notices at the end
of the test suite.
Deprecation notices in the **Remaining/Other** section need some thought.
You have to decide either to:
* update your code to not use deprecated interfaces anymore, thus gaining better
forward compatibility;
* or move them to the **Legacy** section (by using one of the above way).
After reviewing them, you should silence deprecations in the **Legacy** section
if you think they are triggered by tests dedicated to testing deprecated
interfaces. To do so, add the following line at the beginning of your legacy
test case or in the `setUp()` method of your legacy test class:
`$this->iniSet('error_reporting', -1 & ~E_USER_DEPRECATED);`
Last but not least, you should then configure your C.I. to the reporting mode
that is appropriated to your project by setting SYMFONY_DEPRECATIONS_HELPER to
`strict`, `weak` or empty. It is recommended to start with `weak` mode, upgrade
your code as described above, then when the *Remaining/Other* sections are empty,
move to `strict` to keep forward compatibility on the long run.
Commits
-------
acac734 [PhpUnitBridge] new bridge for testing with PHPUnit
This PR was merged into the 2.6 branch.
Discussion
----------
[Security] Fix expectation in a test.
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | -
| License | MIT
| Doc PR | -
This is related to #13466, which worked perfectly fine in 2.3. It breaks in 2.6 since we've changed the way we check for master request.
Commits
-------
8299a44 [Security] Fix expectation in a test.
This PR was merged into the 2.3 branch.
Discussion
----------
[PropertyAccess] refactor type checks
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR | -
#13735 for 2.3
Commits
-------
9cacecb [PropertyAccess] the property path constructor already implements the type check
4e11c07 [PropertyAccess] refactor type checks to remove duplicate logic
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes#13737).
Discussion
----------
[HttpFoundation] Fix getHost and getPort functions in docblock
This fixes the incorrect references to the functions `getClientHost` and `getClientPort` in the docblock for Request::setTrustedHeaderName.
| Q | A
| ------------- | ---
| Fixed tickets | none
| License | MIT
Commits
-------
1ae9f9c [HttpFoundation] Fix getHost and getPort functions in docblock
- fix the binding of listeners on XMLHttpRequest to always use the
addEventListener method. It does not make sense to change it to
attachEvent as it is about binding listeners on DOM elements.
- fix the feature detection for the event binding on DOM elements:
- the attachEvent and addEventListener methods are on DOM elements,
not on the document object
- the standard method should be preferred in IE versions supporting
both methods
- avoid JS errors when XMLHttpRequest is not defined by avoiding to
override its open method when the object is not there (old IE versions
will still not intercept ajax calls though)
This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes#13725).
Discussion
----------
Add phpdoc for SecurityFactoryInterface::getPosition
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
Commits
-------
bcb2e09 Add phpdoc for SecurityFactoryInterface::getPosition
This PR was merged into the 2.3 branch.
Discussion
----------
[Console] make an assertion more precise in testGetOptionDefaults
| Q | A
| ------------- | ---
| Bug fix? | [no]
| New feature? | no]
| BC breaks? | [no]
| Deprecations? | [no]
| Tests pass? | [yes]
| License | MIT
Minor fix, the default values expected in the test were not exactly the same as what is actually returned.
Commits
-------
06a42e1 [Console] fix assertion in testGetOptionDefaults
This PR was merged into the 2.6 branch.
Discussion
----------
Small syntax fix in CHANGELOG
Markdown list items have to start with a space (both render correctly, but this is the standard and consistent with the rest of the file).
| Q | A
| --- | ---
| Fixed tickets | -
| License | MIT
Commits
-------
e45d514 Small syntax fix
This PR was merged into the 2.7 branch.
Discussion
----------
[FrameworkBundle] Check if templating is enabled.
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #13710
| License | MIT
| Doc PR | -
templating can be disabled.
Commits
-------
c75b276 [FrameworkBundle] Check if templating is enabled.
This PR was merged into the 2.6 branch.
Discussion
----------
[HttpKernel] Fixed DumpDataCollector: dump.name for Windows file paths
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes?
| Fixed tickets |
| License | MIT
| Doc PR |
When using VarDumper on Windows files, the automatic "dump.name" generated wrong names.
`dump()` call in:
```
F:\HtDocs\demo\src\Acme\Controller\DemoController.php
```
Displayed:
```
dump()
in :\HtDocs\demo\src\Acme\Controller\DemoController.php line 35
```
Expected result is:
```
dump()
in DemoController.php line 35
```
The existing code in line 118 didn't use the variable from the previous line.
Commits
-------
a025dea Fix dump.name for Windows file paths
This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes#13586).
Discussion
----------
[DX][Config] Changed return type definition for some methods of NodeDefinition
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #12280
| License | MIT
Discussed in #12280
Commits
-------
89ca585 Changed return type definition for some methods of NodeDefinition
This PR was merged into the 2.3 branch.
Discussion
----------
fixed possible race condition when creating a directory
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #13228
| License | MIT
| Doc PR | n/a
Commits
-------
8542866 fixed possible race condition when creating a directory
This PR was merged into the 2.7 branch.
Discussion
----------
[FrameworkBundle] Enable assets by default
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #13667
| License | MIT
| Doc PR | -
This should make the tests pass again.
There are two templates from TwigBundle that are used with functional tests, and require the asset() helper:
* src/Symfony/Bundle/TwigBundle/Resources/views/Exception/exception_full.html.twig
* src/Symfony/Bundle/TwigBundle/Resources/views/layout.html.twig
Commits
-------
f5c0a69 [FrameworkBundle] Enable assets by default.
This PR was merged into the 2.6 branch.
Discussion
----------
[WebProfilerBundle] fix html lint on (other) empty onclick
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
*This is for the empty onclick that appeared in 2.6*
The request collector has an empty onclick="" attribute
when {{ link }} isn't available. This tends to happen when
rendering the debug toolbar.
Commits
-------
58bd16c [WebProfilerBundle] fix html lint on (other) empty onclick
This PR was merged into the 2.3 branch.
Discussion
----------
[WebProfilerBundle] fix html lint on empty onclick
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
The request collector has an empty onclick="" attribute
when {{ link }} isn't available. This tends to happen when
rendering the debug toolbar.
Commits
-------
a3a2f15 [WebProfilerBundle] fix html linting on empty onclick
This PR was submitted for the 2.6 branch but it was merged into the 2.7 branch instead (closes#13692).
Discussion
----------
[Filesystem] Improve exception message for copy method
see diff
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes? (no change in semantics)
| Fixed tickets |
| License | MIT
| Doc PR |
Commits
-------
021206c [Filesystem] Improve exception message for copy method
This PR was merged into the 2.6 branch.
Discussion
----------
[WebProfilerBundle] Fix for broken profiler layout
| Q | A
| ------------- | ---
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | -
| License | MIT
| Doc PR | -
With the latest 2.6 the profiler layout is broken:
I am not sure what broke it...
Commits
-------
af0ea97 Fix for broken profiler layout
This PR was squashed before being merged into the 2.3 branch (closes#13691).
Discussion
----------
[Console] Added a little explaination about Command#interact()
This has confused some long time Symfony users recently: https://twitter.com/jmolivas/status/566283453264850945
| Q | A
| ------------- | ---
| Fixed tickets | -
| License | MIT
Commits
-------
38e7b72 [Console] Added a little explaination about Command#interact()
This PR was submitted for the 2.5 branch but it was merged into the 2.7 branch instead (closes#13615).
Discussion
----------
[FrameworkBundle] Made ServerParams a service
| Q | A
| ------------- | ---
| Bug fix? | [yes]
| New feature? | [no]
| BC breaks? | [no]
| Deprecations? | [no]
| Tests pass? | [yes]
| License | MIT
Since 2.5 we can inject the request stack in ServerParams (see #10912).
Now when a request is handled by HttpFoundationRequestHandler, the content length will be fetched via the current request and not the super global anymore.
Commits
-------
455b714 [FrameworkBundle] Made ServerParams a service
This PR was merged into the 2.7 branch.
Discussion
----------
[2.7] [FrameworkBundle] bugfix in configuration for assets
| 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
If both of configurations are defined, the exception breaks because it isn't
defined properly (missing backslash in FQCN for ```\LogicException```).
Also, the message was wrong (it's referred to "templating.templating" instead of
"framework.templating").
Commits
-------
3b4c23f [2.7] [FrameworkBundle] bugfix in configuration for assets
| 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
If both of configurations are defined, the exception is break because it isn't
defined properly (missing backslash in FQCN for ```\LogicException```).
Also, the message was wrong (it's referred to "templating.templating" instead of
"framework.templating").
