{"action":"closed","issue":{"url":"https://api.github.com/repos/symfony/symfony-docs/issues/6543","repository_url":"https://api.github.com/repos/symfony/symfony-docs","labels_url":"https://api.github.com/repos/symfony/symfony-docs/issues/6543/labels{/name}","comments_url":"https://api.github.com/repos/symfony/symfony-docs/issues/6543/comments","events_url":"https://api.github.com/repos/symfony/symfony-docs/issues/6543/events","html_url":"https://github.com/symfony/symfony-docs/issues/6543","id":153647914,"number":6543,"title":"[RFC] Updating the documentation of the Yaml component","user":{"login":"javiereguiluz","id":73419,"avatar_url":"https://avatars.githubusercontent.com/u/73419?v=3","gravatar_id":"","url":"https://api.github.com/users/javiereguiluz","html_url":"https://github.com/javiereguiluz","followers_url":"https://api.github.com/users/javiereguiluz/followers","following_url":"https://api.github.com/users/javiereguiluz/following{/other_user}","gists_url":"https://api.github.com/users/javiereguiluz/gists{/gist_id}","starred_url":"https://api.github.com/users/javiereguiluz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/javiereguiluz/subscriptions","organizations_url":"https://api.github.com/users/javiereguiluz/orgs","repos_url":"https://api.github.com/users/javiereguiluz/repos","events_url":"https://api.github.com/users/javiereguiluz/events{/privacy}","received_events_url":"https://api.github.com/users/javiereguiluz/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/symfony/symfony-docs/labels/YAML","name":"YAML","color":"dddddd"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-05-08T10:18:45Z","updated_at":"2016-09-01T13:18:50Z","closed_at":"2016-09-01T13:18:50Z","body":"In http://symfony.com/doc/current/components/yaml/introduction.html we explain how to parse and dump using two different methods: `Parser`/`Dump` classes and static methods of `Yaml` class.\r\n\r\nI don't like when we have several ways of doing the same thing ... and I like it less when we don't explain their differences or tell the user when to use each alternative.\r\n\r\nSo I propose the following:\r\n\r\n  * Use the static methods to show the basic usage.\r\n  * Explain the object oriented API later in a new section of that article.\r\n  * Add some info about when to use each alternative. "}}
{"actor":{"display_login":"javiereguiluz"}}