[Yaml] use static Yaml API #6598
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
|
👍 |
| $value = $yaml->parse(file_get_contents('/path/to/file.yml')); | ||
| Because it is currently possible to pass a filename to this method, you | ||
| must validate the input first. Passing a filename is deprecated in | ||
| Symfony 2.2, and will be removed in Symfony 3.0. |
There was a problem hiding this comment.
will be removed -> was removed ?
|
A big 👍 from me! |
|
Thanks Christian. |
wouterj
added a commit
that referenced
this pull request
May 21, 2016
This PR was merged into the 2.3 branch. Discussion ---------- [Yaml] use static Yaml API I don't see a good reasons to explicitly describe the non-static API. If you ever really need to use the `Parser` and `Dumper` classes directly, you will be able to easily figure out how to use them yourself. Commits ------- 7dd4bae use static Yaml API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't see a good reasons to explicitly describe the non-static API. If you ever really need to use the
ParserandDumperclasses directly, you will be able to easily figure out how to use them yourself.