YAML 1.2.2 lets nodes be explicitly typed via tags. Currently any !/!! prefix is treated as plain text.
Request
Parse and honour:
!!str, !!int, !!float, !!bool, !!null — force scalar resolution!!seq, !!map — force collection kind (mostly informational since kind is already implied)!!set — mapping where every value is null, exposed as a hashset-like structure!!omap — sequence of single-pair mappings, exposed as [ordered] hashtable- Verbatim tags
!<tag:...> — accept and ignore (or surface as metadata)
- Local tags
!foo and %TAG directives — accept; behavior TBD
Spec examples covered
- Example 2.21 — Miscellaneous (typed forms with
!!str)
- Example 2.23 — Various Explicit Tags
- Example 2.24 — Global Tags
- Example 2.25 —
!!set
- Example 2.26 —
!!omap
Open questions
- Custom tag handlers (extension API) — likely out of scope for v1.
- Should unknown tags warn or silently fall through to default scalar/collection resolution? Recommend silent fall-through with a debug message.
YAML 1.2.2 lets nodes be explicitly typed via tags. Currently any
!/!!prefix is treated as plain text.Request
Parse and honour:
!!str,!!int,!!float,!!bool,!!null— force scalar resolution!!seq,!!map— force collection kind (mostly informational since kind is already implied)!!set— mapping where every value is null, exposed as a hashset-like structure!!omap— sequence of single-pair mappings, exposed as[ordered]hashtable!<tag:...>— accept and ignore (or surface as metadata)!fooand%TAGdirectives — accept; behavior TBDSpec examples covered
!!str)!!set!!omapOpen questions