emptyMappingValues

Reports empty mapping values.

✅ This rule is included in the yaml logical presets.

Empty values in YAML mappings can lead to unexpected runtime behavior. Parsers may interpret them as null, empty strings, or other values depending on the implementation. If an empty value is intentional, use an explicit null to clarify intent.

Examples

❌ Incorrect

name:

config:
  host:
  port: 8080

✅ Correct

name: null

name: ""

config:
  host: localhost
  port: 8080

Options

This rule is not configurable.

When Not To Use It

If your project intentionally uses empty mapping values to represent null values and you have consistent parser behavior, you may not need this rule. Projects with established conventions around implicit null values in YAML may also choose to disable this rule.

Further Reading

• YAML Specification - Mapping

Equivalents in Other Linters

• ESLint: yml/no-empty-mapping-value