diogo/symfony
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

minor #14666 [UPGRADE] Mention the CSS strategy and it's effects (WouterJ)

Browse Source 
This PR was squashed before being merged into the 2.7 branch (closes #14666).

Discussion
----------

[UPGRADE] Mention the CSS strategy and it's effects

The CSS strategy, which is automatically applied to Twig CSS files as of Symfony 2.7, results in different behaviour when outputting reserved characters like `#123456`. This has to be documented in the UPGRADE file.

See https://github.com/javiereguiluz/EasyAdminBundle/pull/305 for an example.

| Q | A
| --- | ---
| Fixed tickets | -
| License | MIT

Commits
-------

8b891ff [UPGRADE] Mention the CSS strategy and it's effects
This commit is contained in:
Fabien Potencier 2015-05-20 10:13:43 +02:00
commit aca6ff6a7a
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
UPGRADE-2.7.md
View File

@ -534,3 +534,33 @@ Validator
* The PHP7-incompatible constraints (Null, True, False) and related validators
(NullValidator, TrueValidator, FalseValidator) are marked as deprecated
in favor of their `Is`-prefixed equivalent.
TwigBundle
----------
* The `Symfony\Bundle\TwigBundle\TwigDefaultEscapingStrategy` is deprecated and no longer
used in favor of `Twig_FileExtensionEscapingStrategy`. This means that CSS files automatically
use the CSS escape strategy. This can cause different behaviour when outputting reserved
characters.
Before:
```css
{# styles.css.twig #}
{# with brand_color: '#123456' #}
body {
background: {{ brand_color }};
}
```
After:
```css
{# styles.css.twig #}
{# with brand_color: '#123456' #}
body {
background: {{ brand_color|raw }};
}
```