Skip to content

[Yaml] sync changelog and upgrade files #16654

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 25, 2015
Merged

[Yaml] sync changelog and upgrade files #16654

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
8 changes: 8 additions & 0 deletions UPGRADE-2.8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -505,3 +505,11 @@ Config
Additionally, if you have implemented cache validation strategies *using* `isFresh()`
yourself, you should have a look at the new cache validation system based on
`ResourceChecker`s.

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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should enclose these Yaml strings in backticks to make them code blocks (otherwise the double backslash will not appear as it will be considered as a markdown escaping)

5 changes: 5 additions & 0 deletions UPGRADE-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1228,6 +1228,11 @@ UPGRADE FROM 2.x to 3.0

### Yaml

* 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not deprecated in 3.0. The deprecation is in 2.8

("Foo\Var" is not valid whereas "Foo\\Var" is)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here


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

Before:
Expand Down
3 changes: 2 additions & 1 deletion src/Symfony/Component/Yaml/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@ CHANGELOG
2.8.0
-----

* Deprecated usage of @ and \` at the beginning of an unquoted string
* 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)

Expand Down