-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathtest.yml
131 lines (115 loc) · 3.75 KB
/
test.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
#Comments begin with the number sign (#), can start anywhere on a line and continue until
#the end of the line. Comments must be separated from other tokens by whitespace characters.
#If characters appear inside of a string, then they are number sign (#) literals.
#Scalar content can be written in block notation, using a literal style (indicated by “|”)
#where all line breaks are significant. Alternatively, they can be written with the folded
#style (denoted by “>”) where each line break is folded to a space unless it ends an empty
#or a more-indented line.
# data: |
# There once was > [] a tall man from Ealing
# Who got on a bus to Darjeeling
# It said on the door
# "Please don't sit on the floor"
# So he carefully sat on the ceiling
# data: >
# Wrapped text
# will be folded
# into a single
# paragraph
# Blank lines denote
# paragraph breaks
#List members are denoted by a leading hyphen (-) with one member per line.
shopping_list:
- tea
- milk
- coffee
#A list can also be specified by enclosing text in square brackets ([...]) with each entry
#separated by a comma. Example below
list:
- ["Item 1", "Item2"]
- ["Item 3", "Item3"]
- [name, age, skills]: [John, 34, a lot of things]
employees:
- name: John Smith
age: 33
- name: John Doe
age: 41
#An associative array can also be specified by text enclosed in curly braces ({...}), with
#keys separated from values by colon and the entries separated by commas (spaces are not
#required to retain compatibility with JSON).
example2:
- {name: John Smith, age: 33}
- {name: John Doe, age: 41}
- ["Item 1", "Item2"]
#YAML requires the colon be followed by a space so that url-style strings like
#http://www.wikipedia.org can be represented without needing to be enclosed in quotes.
website: http://www.wikipedia.org
#Strings (one type of scalar in YAML) are ordinarily unquoted, but may be enclosed in double
#-quotes ("), or single-quotes (').
stringtest:
example1: So this should be a string
example2: "but this should be a string as well"
example3: 'and this too'
example4: and I'd think that it can have any > type | of character ...
example5: '#dfdfd' and hello's '#000000' "'hello'#test" #test
example6: "#ff9d9d" #inline comment
#Lists of numerical arrays will automatically be converted to matrices
test:
matrix:
- [0, 1, 2]
- [3, 4, 5]
- [6, 7, 8]
array: [0, 1, 2]
now:
what:
if:
we:
go:
very:
many:
levels:
note: "what will happen then?"
example1:
- name: John Smith
age: 33
- name: John Doe,
age: 41
example:
- martin:
name: Martin D'vloper
job: Developer
skills:
- python: good
- perl: good
- pascal: moderate
- tabitha:
name: Tabitha Bitumen
job: Developer
skills:
- lisp: good
- fortran: moderate
- erlang: novice
#TO DO
# #Multiple documents within a single stream are separated by three hyphens (---).
# ---
# Test:
#Scalar content can be written in block notation, using a literal style (indicated by “|”)
#where all line breaks are significant. Alternatively, they can be written with the folded
#style (denoted by “>”) where each line break is folded to a space unless it ends an empty
#or a more-indented line.
#
# Test:
# Note: So this should be a different document then?
# data: |
# There once was a tall man from Ealing
# Who got on a bus to Darjeeling
# It said on the door
# "Please don't sit on the floor"
# So he carefully sat on the ceiling
# data: >
# Wrapped text
# will be folded
# into a single
# paragraph
# Blank lines denote
# paragraph breaks