YAML files are supposed to be able to begin with ---, and yamllint recommends this rule to ensure that many YAML files behave well when concatenated together. However, CloudABI's YAML parsing setup requires its YAML files to begin like %TAG ! tag:nuxi.nl,2015:cloudabi/, and then a document delimiter and capability spec document can follow.
Would it be possible to enhance the capability spec so that --- can lead the very beginning of .YML files, matching how other applications process YAML files?
I learned something today: %TAG seems to define a global YAML thing, separate from the document-by-document bits. And in fact, yamllint has no quarrel with this!
YAML files are supposed to be able to begin with
---
, and yamllint recommends this rule to ensure that many YAML files behave well when concatenated together. However, CloudABI's YAML parsing setup requires its YAML files to begin like%TAG ! tag:nuxi.nl,2015:cloudabi/
, and then a document delimiter and capability spec document can follow.Would it be possible to enhance the capability spec so that
---
can lead the very beginning of .YML files, matching how other applications process YAML files?