Skip to main content


Laurence MorganAbout 1 min


YAML Ain't Markup Language (YAML)


YAML support within Murex is pretty mature however it is not considered a primitive. Which means, while it is a recommended builtin which you should expect in most deployments of Murex, it's still an optional package and thus may not be present in some edge cases. This is because it relies on external source packages for the shell to compile.

Default Associations

  • Extension: yaml
  • Extension: yml
  • MIME: application/x-yaml
  • MIME: application/yaml
  • MIME: text/x-yaml
  • MIME: text/yaml

Supported Hooks

  • Marshal() Supported
  • ReadArray() Works with YAML arrays. Maps are converted into arrays
  • ReadArrayWithType() Works with YAML arrays. Maps are converted into arrays. Element type returned in Murex should match element type in YAML
  • ReadIndex() Works against all properties in YAML
  • ReadMap() Works with YAML maps
  • ReadNotIndex() Works against all properties in YAML
  • Unmarshal() Supported
  • WriteArray() Works with YAML arrays

See Also

  • [[ Element ]]: Outputs an element from a nested structure
  • cast: Alters the data type of the previous function without altering it's output
  • format: Reformat one data-type into another data-type
  • json: JavaScript Object Notation (JSON)
  • jsonl: JSON Lines
  • open: Open a file with a preferred handler
  • runtime: Returns runtime information on the internal state of Murex
  • index: Outputs an element from an array, map or table

Read more about type hooks

This document was generated from builtins/types/yaml/yaml_doc.yamlopen in new window.

Last update:
Contributors: Laurence Morgan,Laurence Morgan,Laurence