Task #33268

Document new YAML behaviour for Upgrade to 1.1

Added by Christopher Hlubek almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Must have
Category:
Configuration
Start date:
2012-01-17
Due date:
% Done:

100%

Estimated time:
Sprint:
PHP Version:
Has patch:
No
Complexity:

Description

The YAML parser changed its behaviour in some intricate ways. One of it is the (now correct) processing of escape sequences within double quoted strings (http://yaml.org/spec/1.2/spec.html#id2787109).

Unfortunately some FLOW3 users could have used the double quote syntax to express object names or pointcut expressions (e.g. in a Policy file) where the escape sequence could produce an unwanted result and AOP or security fails silently.

resources:
  methods:
    Foo_Bar: "method(MyPackage\Domain\Model\Poo->test()" 

The class would not match MyPackage\Domain\Model\Poo but rather MyPackage\Domain\Model?oo. To use double quoted strings the \ character would need to be escaped with another backslash.

We should document the new behaviour and discourage usage of double quotes in YAML files as a CGL. Additionaly we could think about a migration script for configuration files.

Also available in: Atom PDF