YAML Explicit and Local Tags
Explicit tags across the standard set — !!str, !!float, !!int, !!bool, !!null, !!binary, !!timestamp, !!omap, !!set — alongside two application-local ! tags. CI dialects use local tags in the wild, so a pipeline parser has to decide whether to reject, ignore, or resolve them.
# Explicit tags. The !! prefix names a type from the YAML tag repository; a single ! names an
# application-local tag that a generic loader has no constructor for. CI dialects use local tags
# in the wild (GitLab's !reference is the well-known one), so a pipeline parser has to decide
# whether to reject, ignore, or resolve them.
explicit_string: !!str 12345
explicit_float: !!float 3
explicit_int: !!int "42"
explicit_bool: !!bool "true"
explicit_null: !!null null
binary_payload: !!binary |
aGVsbG8gd29ybGQK
timestamp: !!timestamp 2026-01-15T09:30:00Z
ordered_pairs: !!omap
- build: 1
- test: 2
unique_values: !!set
? build
? test
local_tag_scalar: !Severity high
local_tag_mapping: !Stage
name: build
order: 1
untagged_control:
name: build
order: 1
Specifications
- Standard Tags
- 9
- Local Tags
- 2
- Has Binary Tag
- true
- Has Omap
- true
- Has Set
- true
- Edge Case
- generic loaders have no constructor for a local ! tag
- First Local Tag At Line
- 24
Testing contract
Expected to recover- Scenario
- Load a document mixing standard YAML tags with application-local ones
- Expected result
- !!str 12345 loads as the string "12345" and !!binary decodes to the bytes of "hello world\n", while an unregistered !Severity tag raises or is preserved rather than silently dropped
What is a .yaml file?
YAML (YAML Ain't Markup Language) is a human-readable data-serialization format using indentation, key-value pairs, and lists, and is a superset of JSON. It supports comments, anchors, and multiple documents per file, favoring readability for configuration. Its indentation sensitivity makes it error-prone to hand-edit.
How to use this file
Use an example YAML file to test config parsers, indentation and anchor handling, multi-document streams, and safe-loading to avoid arbitrary object construction.
How to use this file for testing
“YAML Explicit and Local Tags” is a deterministic Novus Examples fixture for Config parsing, Encoding detection, Editor testing. TOML and INI configuration files with nested sections and typed values — for testing config parsers and loaders.
Documented properties for this file: YAML · 778 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Code examples
import yaml # pip install pyyaml
with open("explicit-and-local-tags.yaml") as f:
data = yaml.safe_load(f)
print(data)Related files
- yamlYAML Anchors and AliasesAnchors and aliases across mapping, sequence and scalar nodes, including an anchor nested inside another anchored node. The point most tooling misses: an alias is a reference to the same node, so a shallow-loading parser can share mutable state between jobs.
- yamlYAML Block Scalars and Chomping IndicatorsEvery block-scalar variation in one file: literal and folded styles, all three chomping indicators, an explicit indentation indicator, a folded block with a paragraph break, and an embedded shell-shaped script whose own indentation must survive.
- yamlYAML Bounded Anchor ReuseNested anchor reuse kept deliberately small: two anchors, six references, thirty-one expanded nodes. It is here to test alias resolution and expansion accounting on a safe input, and is explicitly not a billion-laughs expansion bomb.
- yamlYAML Directives and CommentsA two-document stream where each document declares its own %YAML directive and the second adds a %TAG handle used by a local tag. Comments appear in every position they are legal, and every one of them is lost by a non-round-tripping loader.
- yamlYAML Duplicate KeysDuplicate keys at three nesting levels, including a duplicated top-level sequence. The spec forbids them; most loaders keep the last silently, a few keep the first, and strict linters reject the document. The file publishes the last-wins answer.
- yamlYAML Flow and Block StylesFlow (JSON-like) and block collections expressing the same structures, nested inside one another in both directions, plus a flow mapping wrapped across lines and a line of strict JSON — which is valid YAML, and a useful check on a parser's JSON-subset claim.
Generated by generation/pipelines.py. Free for any use, no attribution required — license.