You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I 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.
So I propose the following:
Use the static methods to show the basic usage.
Explain the object oriented API later in a new section of that article.
Add some info about when to use each alternative.
The text was updated successfully, but these errors were encountered:
Oh, I completely missed this issue when creating #6598. So the first task is checked now anyway.
However, I don't think we really need to explain the internal API. I cannot think of a use case that justifies using the Parser or Dumper class directly that is so common that we should include it in the documentation. Developers who are in the need of using the classes directly will still be able to figure out how to do that themselves.
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 ofYaml
class.I 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.
So I propose the following:
The text was updated successfully, but these errors were encountered: