Wump's configuration is written inside of
YAML, a "human friendly data serialization" language.
The reason why Wump uses YAML is that it's an easy to read and edit data serialization language (and it's my primary data serialization language)
Below are some examples on how YAML looks
strings.yaml# Strings can be written in plain key: value# But it's preffered to put them inside of apostropheskey: 'value'# To escape an apostrophe, you can simply use 2 of themkey: 'Value''s sheep'# You can make a multi-line using the > (mt/more than) symbolkey: >value# Or you can add a \n after every line using the | (pipe) symbolkey: |value# You can also use " (double quotes)key: "Several lines of text,\ncontaining \"double quotes\". Escapes (like \\n) work.\nIn addition,\nnewlines can be esc\\naped to prevent them from being converted to a space.\n\nNewlines can also be added by leaving a blank line.\nLeading whitespace on lines is ignored."\n
types.yml# Some of the types that YAML supports:string: 'hello'boolean: trueinteger: 1float: 1.1null: nullobject:key: 'value'array:- 'entry'
objects.yml# YAML is sensetive about spaces, here's an example of a parent with 2 childsparent:key: 'value'child:sibling:key: 'value'child:key: 'value'
If a file only includes an array, it'll export as an array.
array.yml- 'This file'- 'Exports as an array'- true- 10
array.js['This file','Exports as an array'true10];
array.yml# Arrays are written like thisparent:# An array with objectschild:- object: 1- object: 2child:# An array with a number and boolean insidearray:- 1- true