![Switch to use YAML Literal Style format to fix issues with implicit keys in the updates_checklist.yml file [#3273453] | Drupal.org Switch to use YAML Literal Style format to fix issues with implicit keys in the updates_checklist.yml file [#3273453] | Drupal.org](https://www.drupal.org/files/issues/2022-04-05/yarn-lint-yaml--for-checklist-updates-2022-04-05_12-17.png)
Switch to use YAML Literal Style format to fix issues with implicit keys in the updates_checklist.yml file [#3273453] | Drupal.org
Preserve a YAML 'literal block' (using |), or a 'folded block' (using '>') · Issue #36 · kislyuk/yq · GitHub
![Literal colon character (":") in expressions kills YAML parser · Issue #1019 · actions/runner · GitHub Literal colon character (":") in expressions kills YAML parser · Issue #1019 · actions/runner · GitHub](https://user-images.githubusercontent.com/2090382/112238923-f5285980-8c1b-11eb-8ce4-b5d06ce2a4b0.png)
Literal colon character (":") in expressions kills YAML parser · Issue #1019 · actions/runner · GitHub
![Why should we prefer the YAML file over the properties file for configurations in Spring Boot projects? | by Saeed Zarinfam | ITNEXT Why should we prefer the YAML file over the properties file for configurations in Spring Boot projects? | by Saeed Zarinfam | ITNEXT](https://miro.medium.com/v2/resize:fit:432/1*p2aE1t0-YMoYJyEkIjQQ2w.png)
Why should we prefer the YAML file over the properties file for configurations in Spring Boot projects? | by Saeed Zarinfam | ITNEXT
![Azure DevOps – Tips and Tricks – 7 – Resolve the “While scanning a literal block scalar, found extra spaces in first line” error. – Praveen Kumar Sreeram's Blog Azure DevOps – Tips and Tricks – 7 – Resolve the “While scanning a literal block scalar, found extra spaces in first line” error. – Praveen Kumar Sreeram's Blog](https://praveenkumarsreeram.files.wordpress.com/2022/05/2.-azure-devops-e28093-tips-and-tricks-e28093-7-e28093-resolve-the-while-scanning-a-literal-block-scalar-found-extra-spaces-in-first-line-empty-line.png?w=1024)