Document new YAML behaviour for Upgrade to 1.1
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.