Introduce YAML dumper flags #17520
Comments
|
👍 |
|
see #17578 |
|
I'd like to work on this feature. Can I or is there already some work in progress? |
|
👍 |
xabbuh
added a commit
that referenced
this issue
Feb 5, 2016
…bbuh) This PR was merged into the 3.1-dev branch. Discussion ---------- [Yaml] dump customization option with dumper flags | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | yes | Tests pass? | yes | Fixed tickets | #17520 | License | MIT | Doc PR | TODO Commits ------- 286103b [Yaml] dump customization option with dumper flags
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Frequently we get requests asking for how specifc object structures should be dumped to YAML (for examples, see #16266 and #17391, but there are more of them). We always were reluctant to implement these features as they would either have meant BC breaks (because of semantic changes to the dumped YAML) or because the semantics did not change (changes were merely aesthetic).
Maybe it's time we break with this and introduce dumper flags that control how YAML strings are dumped (similar to what was recently done for the VarDumper component in #17305). This would allow users to influence the dumped YAML without requiring us to introduce lots of additional parameters (the
$objectSupportargument could be replaced with the dumper flags argument).The text was updated successfully, but these errors were encountered: