Now as far as YAML,
this is the slide, I should say, represents a sort of Cliffs Notes.
Just what do you need to know about the YAML syntax?
I know I've mentioned this stuff already in part in my previous demos,
but this YAML file, which could have the YAML or YML
extension, I myself like the three‑character extension, starts
with three hyphens to denote the start.
And also at the end,
you can use it as a separator, but definitely at the start
of the document. Comments or line comments are preceded by
a hash sign or an octothorpe.
The main idea, similar to how JSON represents data, is you've got one
or more key value pairs. But notice that we're not using a comma to
separate them, and we're not even putting them in braces of any type
like we would with JSON. Now whereas JSON ignores whitespace; YAML is
all about the whitespace. That is, you need to use consistent
indentation.
The normal is two characters indent at each level.
And as long as you're consistent throughout the document, YAML won't complain.
So if you choose a longer than two character of indent length,
that's fine. Just be consistent throughout your definitions.
And as you can see,
I'm just calling out that you can do some more complex data structures here,
like nested key value arrays, lists I've mentioned. The standard
data types are supported in the YAML schema.
You've got datetime up above.
I went through the different keys up there,
key value pairs. Notice there's examples of integer,
decimal, and Boolean.