Skip to content

[Yaml] more fixes to changelog and upgrade files #16662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 28, 2015
Merged

[Yaml] more fixes to changelog and upgrade files #16662

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions UPGRADE-2.8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -511,5 +511,17 @@ Yaml

* Deprecated usage of a colon in an unquoted mapping value
* Deprecated usage of `@`, `` ` ``, `|`, and `>` at the beginning of an unquoted string
* Deprecated non-escaped \ in double-quoted strings when parsing Yaml
("Foo\Var" is not valid whereas "Foo\\Var" is)
* When surrounding strings with double-quotes, you must now escape `\` characters. Not
escaping those characters (when surrounded by double-quotes) is deprecated.

Before:

```yml
class: "Foo\Var"
```

After:

```yml
class: "Foo\\Var"
```
17 changes: 15 additions & 2 deletions UPGRADE-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1230,8 +1230,21 @@ UPGRADE FROM 2.x to 3.0

* Using a colon in an unquoted mapping value leads to a `ParseException`.
* Starting an unquoted string with `@`, `` ` ``, `|`, or `>` leads to a `ParseException`.
* Deprecated non-escaped \ in double-quoted strings when parsing Yaml
("Foo\Var" is not valid whereas "Foo\\Var" is)
* When surrounding strings with double-quotes, you must now escape `\` characters. Not
escaping those characters (when surrounded by double-quotes) leads to a `ParseException`.

Before:

```yml
class: "Foo\Var"
```

After:

```yml
class: "Foo\\Var"
```


* The ability to pass file names to `Yaml::parse()` has been removed.

Expand Down
16 changes: 14 additions & 2 deletions src/Symfony/Component/Yaml/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,20 @@ CHANGELOG

* Deprecated usage of a colon in an unquoted mapping value
* Deprecated usage of @, \`, | and > at the beginning of an unquoted string
* Deprecated non-escaped \ in double-quoted strings when parsing Yaml
("Foo\Var" is not valid whereas "Foo\\Var" is)
* When surrounding strings with double-quotes, you must now escape `\` characters. Not
escaping those characters (when surrounded by double-quotes) is deprecated.

Before:

```yml
class: "Foo\Var"
```

After:

```yml
class: "Foo\\Var"
```

2.1.0
-----
Expand Down