-
Notifications
You must be signed in to change notification settings - Fork 0
/
objects.feature
309 lines (300 loc) · 6.67 KB
/
objects.feature
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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
Feature: Object types
Scenario: object
Given a YAML schema:
```
type: object
```
Then it should accept:
```
key: value
another_key: another_value
```
And it should accept:
```
Sun: 1.9891e30
Jupiter: 1.8986e27
Saturn: 5.6846e26
Neptune: 10.243e25
Uranus: 8.6810e25
Earth: 5.9736e24
Venus: 4.8685e24
Mars: 6.4185e23
Mercury: 3.3022e23
Moon: 7.349e22
Pluto: 1.25e22
```
# Unlike JSON, YAML allows numeric keys, which are treated as strings
And it should accept:
```
0.01: cm
1: m
1000: km
```
But it should NOT accept:
```
"Not an object"
```
And it should NOT accept:
```
["An", "array", "not", "an", "object"]
```
Scenario: properties
Given a YAML schema:
```
type: object
properties:
number:
type: number
street_name:
type: string
street_type:
enum: [Street, Avenue, Boulevard]
```
Then it should accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
```
# If we provide the number in the wrong type, it is invalid:
But it should NOT accept:
```
number: "1600"
street_name: Pennsylvania
street_type: Avenue
```
# By default, leaving out properties is valid
And it should accept:
```
number: 1600
street_name: Pennsylvania
```
# By extension, even an empty object is valid
And it should accept:
```
{}
```
# By default, providing additional properties is valid
And it should accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
direction: NW
```
Scenario: Pattern properties
Given a YAML schema:
```
type: object
patternProperties:
^S_:
type: string
^I_:
type: integer
```
Then it should accept:
```
S_25: This is a string
```
And it should accept:
```
I_0: 42
```
# If the name starts with S_, it must be a string
But it should NOT accept:
```
S_0: 42
```
# If the name starts with I_, it must be an integer
And it should NOT accept:
```
I_42: This is a string
```
# This is a key that doesn't match any of the regular expressions
But it should accept:
```
keyword: value
```
Scenario: Additional properties
Given a YAML schema:
```
type: object
properties:
number:
type: number
street_name:
type: string
street_type:
enum: [Street, Avenue, Boulevard]
additionalProperties: false
```
Then it should accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
```
# Since additionalProperties is false, an extra property "direction" makes the object invalid:
But it should NOT accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
direction: NW
```
Scenario: additionalProperties as a schema
Given a YAML schema:
```
type: object
properties:
number:
type: number
street_name:
type: string
street_type:
enum: [Street, Avenue, Boulevard]
additionalProperties:
type: string
```
Then it should accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
```
# This is valid, since the additional property's value is a string:
And it should accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
direction: NW
```
# This is invalid, since the additional property's value is not a string:
And it should NOT accept:
```
number: 1600
street_name: Pennsylvania
street_type: Avenue
office_number: 201
```
Scenario: Additional properties with properties and patternProperties
Given a YAML schema:
```
type: object
properties:
builtin:
type: number
patternProperties:
^S_:
type: string
^I_:
type: integer
additionalProperties:
type: string
```
Then it should accept:
```
builtin: 42
```
# This is a key that doesn't match any of the regular expressions
And it should accept:
```
keyword: value
```
# It must be a string, not an integer
And it should NOT accept:
```
keyword: 42
```
Scenario: Required properties
Given a YAML schema:
```
type: object
properties:
name:
type: string
email:
type: string
address:
type: string
telephone:
type: string
required:
- name
- email
```
Then it should accept:
```
name: William Shakespeare
email: [email protected]
```
# Providing extra properties is fine, even properties not defined in the schema:
And it should accept:
```
name: William Shakespeare
email: [email protected]
address: Henley Street, Stratford-upon-Avon, Warwickshire, England
authorship: in question
```
# Missing the required "email" property makes the YAML document invalid:
But it should NOT accept:
```
name: William Shakespeare
address: Henley Street, Stratford-upon-Avon, Warwickshire, England
```
# A property with a null value is considered not being present:
And it should NOT accept:
```
name: William Shakespeare
address: Henley Street, Stratford-upon-Avon, Warwickshire, England
email: null
```
Scenario: Property names
Given a YAML schema:
```
type: object
propertyNames:
pattern: "^[A-Za-z_][A-Za-z0-9_]*$"
```
Then it should accept:
```
_a_proper_token_001: "value"
```
But it should NOT accept:
```
-001 invalid: "value"
```
Scenario: Size
Given a YAML schema:
```
type: object
minProperties: 2
maxProperties: 3
```
Then it should NOT accept:
```
{}
```
And it should NOT accept:
```
a: 0
```
But it should accept:
```
a: 0
b: 1
```
And it should accept:
```
a: 0
b: 1
c: 2
```
But it should NOT accept:
```
a: 0
b: 1
c: 2
d: 3
```