3 ms·
I enjoy that you're scolding me about 'not reading' after doubling down the accuracy of your initial post, which, yes, I can easily imagine you did from your ph
by mdaniel 2y ago
I enjoy that you're scolding me about 'not reading' after doubling down the accuracy of your initial post, which, yes, I can easily imagine you did from your phone
And yet I brought receipts for my claims, and you just bring "reed the manul, n00b"
- hnlmorg 2y agoFirstly, I didn't say "read the manual", I said "read the links I shared". And that's a pretty reasonable comment to make given I took the time to find examples knowing that I couldn't easily type them out on my phone. And if you bothered to open the links you'd realize they were brief and to the point. I was actually trying to be helpful. Secondly, your "receipts" were incorrect. Neither of your examples follows the examples I cited, and your second example creates a key named "Description:>-", which is clearly wrong. Hence why ">-" needs to be after the colon. Here is more examples and evidence of how to use >- and why your "receipts" were also incorrect: https://go.dev/play/p/1B4ba-dUARq https://go.dev/play/p/1B4ba-dUARq Here you can clearly see my example: Foo: >- hello world produces: { "Foo": "hello world" } which is correct. Whereas your example: Bar:>-: hello world produces { "Bar:\u003e-": "hello world" } which is incorrect. ---- One final point: I don't understand why you're being so argumentative here. I posted a lesser-known YAML feature in case it helps some people and you've turned it into some kind of pissing match based on bad-faith interpretations of my comments. There was no need for you to do that.