AverageMarcus/blog
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Update broken links

Browse Source 
Signed-off-by: Marcus Noble <github@marcusnoble.co.uk>
This commit is contained in:
Marcus Noble 2024-05-21 15:24:06 +01:00
parent bdd2e8c79a
commit d48d4dcb14
Signed by: AverageMarcus
GPG Key ID: B8F2DB8A7AEBAF78
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/posts/2021-05-11-yaml-key-spaces.md
View File

@ -23,9 +23,10 @@ I found myself staring at this for a while, followed by searching the [Home Assi
And then it dawned on me! As all JSON is valid YAML, and JSON keys can be pretty much any string it makes sense that YAML supports it.
The above example converted to JSON using [json2yaml](https://www.json2yaml.com/convert-yaml-to-json) looks like this:
The above example converted to JSON using [yq](https://mikefarah.gitbook.io/yq) looks like this:
```json
// yq config.yaml -o json
{
"automation": "../automations.yaml",
"automation split": "../automations"
@ -62,7 +63,7 @@ JSON:
}
```
Depending on the library used, varying results can be generated. For example, [yamlonline](https://yamlonline.com/) returns the following for the same input:
Depending on the library used, varying results can be generated. For example, yamlonline (update: website no longer online) returns the following for the same input:
```json
{