middleman-versions 1.0.0 → 1.0.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: dc29a097675e1b478a5c5dd6064b194f3e0639ff
4
- data.tar.gz: cdaf29ebcbeae782eea896914007575e36768bbc
3
+ metadata.gz: eeb11f7ba271a3821964c6430cf44e4f30815a9d
4
+ data.tar.gz: 709ef8e2b9bcad0a0b85dfcc2686e8207111dec6
5
5
  SHA512:
6
- metadata.gz: 700b08cf243e77f92c3484807eec7b593629ca77f06de26f53dc9c5edfcdf8b684fcf317c3ace38bec369645b5777f5d5a67f0a3fc19468e3f88691c673fb6bb
7
- data.tar.gz: 4df9e19ba9916467ead7c512513abf23279e31c621328532842fa08a64930dc932da3e44d763d3bca0223b66ab5639e4aedd0c191f329946a41468e626a4e5b3
6
+ metadata.gz: 066d16b722fa7e03777b31a2977430ac97ab74a47ae5b9a2294c4f43d3960fe57c0109ed964e9ffced12c45e68657e0298e82299c69ef7ed857a8c6e4c3e4f40
7
+ data.tar.gz: 70029b64b228b700c40ce9ab5e174d9cc3a7d5d3cb9d6916f3dfb37fd3dddda065137339cfcc1684c0995402c1f88ff08ad49174d87a233c69e1efc47da20d5d
data/README.md CHANGED
@@ -1,6 +1,13 @@
1
1
  #middleman-versions
2
2
  Compile different middleman site versions with custom data injected in each one
3
3
 
4
+ ##Dependencies
5
+
6
+ * Middleman <= 4.0.0
7
+
8
+ This Extension use app.proxy to inject values in templates, in Middleman v4 options hash was removed from proxy, https://github.com/middleman/middleman/blob/7c968b9572923fd0f7fb176ca8e52a91727adf84/CHANGELOG.md
9
+
10
+
4
11
  ## How to use it
5
12
  * Add gem to your Gemfile
6
13
 
@@ -1,32 +1,574 @@
1
- ---
2
- routes:
3
- - url_parameters:
4
- id: Esta es el id del usuario que queremos modificar
5
- body:
6
- mandatory_parameters:
1
+ swagger: "2.0"
2
+ info:
3
+ description: |
4
+ [Learn about Swagger](http://swagger.io) or join the IRC channel `#swagger` on irc.freenode.net.
5
+
6
+ For this sample, you can use the api key `special-key` to test the authorization filters
7
+ version: "1.0.0"
8
+ title: Swagger Petstore
9
+ termsOfService: http://helloreverb.com/terms/
10
+ contact:
11
+ name: apiteam@swagger.io
12
+ license:
13
+ name: Apache 2.0
14
+ url: http://www.apache.org/licenses/LICENSE-2.0.html
15
+ host: petstore.swagger.io
16
+ basePath: /v2
17
+ schemes:
18
+ - http
19
+ paths:
20
+ /pets:
21
+ post:
22
+ tags:
23
+ - pet
24
+ summary: Add a new pet to the store
25
+ description: ""
26
+ operationId: addPet
27
+ consumes:
28
+ - application/json
29
+ - application/xml
30
+ produces:
31
+ - application/json
32
+ - application/xml
33
+ parameters:
34
+ - in: body
35
+ name: body
36
+ description: Pet object that needs to be added to the store
37
+ required: false
38
+ schema:
39
+ $ref: "#/definitions/Pet"
40
+ responses:
41
+ "405":
42
+ description: Invalid input
43
+ security:
44
+ - petstore_auth:
45
+ - write_pets
46
+ - read_pets
47
+ put:
48
+ tags:
49
+ - pet
50
+ summary: Update an existing pet
51
+ description: ""
52
+ operationId: updatePet
53
+ consumes:
54
+ - application/json
55
+ - application/xml
56
+ produces:
57
+ - application/json
58
+ - application/xml
59
+ parameters:
60
+ - in: body
61
+ name: body
62
+ description: Pet object that needs to be added to the store
63
+ required: false
64
+ schema:
65
+ $ref: "#/definitions/Pet"
66
+ responses:
67
+ "405":
68
+ description: Validation exception
69
+ "404":
70
+ description: Pet not found
71
+ "400":
72
+ description: Invalid ID supplied
73
+ security:
74
+ - petstore_auth:
75
+ - write_pets
76
+ - read_pets
77
+ /pets/findByStatus:
78
+ get:
79
+ tags:
80
+ - pet
81
+ summary: Finds Pets by status
82
+ description: Multiple status values can be provided with comma seperated strings
83
+ operationId: findPetsByStatus
84
+ produces:
85
+ - application/json
86
+ - application/xml
87
+ parameters:
88
+ - in: query
89
+ name: status
90
+ description: Status values that need to be considered for filter
91
+ required: false
92
+ type: array
93
+ items:
94
+ type: string
95
+ collectionFormat: multi
96
+ responses:
97
+ "200":
98
+ description: successful operation
99
+ schema:
100
+ type: array
101
+ items:
102
+ $ref: "#/definitions/Pet"
103
+ "400":
104
+ description: Invalid status value
105
+ security:
106
+ - petstore_auth:
107
+ - write_pets
108
+ - read_pets
109
+ /pets/findByTags:
110
+ get:
111
+ tags:
112
+ - pet
113
+ summary: Finds Pets by tags
114
+ description: Muliple tags can be provided with comma seperated strings. Use tag1, tag2, tag3 for testing.
115
+ operationId: findPetsByTags
116
+ produces:
117
+ - application/json
118
+ - application/xml
119
+ parameters:
120
+ - in: query
121
+ name: tags
122
+ description: Tags to filter by
123
+ required: false
124
+ type: array
125
+ items:
126
+ type: string
127
+ collectionFormat: multi
128
+ responses:
129
+ "200":
130
+ description: successful operation
131
+ schema:
132
+ type: array
133
+ items:
134
+ $ref: "#/definitions/Pet"
135
+ "400":
136
+ description: Invalid tag value
137
+ security:
138
+ - petstore_auth:
139
+ - write_pets
140
+ - read_pets
141
+ /pets/{petId}:
142
+ get:
143
+ tags:
144
+ - pet
145
+ summary: Find pet by ID
146
+ description: Returns a pet when ID < 10. ID > 10 or nonintegers will simulate API error conditions
147
+ operationId: getPetById
148
+ produces:
149
+ - application/json
150
+ - application/xml
151
+ parameters:
152
+ - in: path
153
+ name: petId
154
+ description: ID of pet that needs to be fetched
155
+ required: true
156
+ type: integer
157
+ format: int64
158
+ responses:
159
+ "404":
160
+ description: Pet not found
161
+ "200":
162
+ description: successful operation
163
+ schema:
164
+ $ref: "#/definitions/Pet"
165
+ "400":
166
+ description: Invalid ID supplied
167
+ security:
168
+ - api_key: []
169
+ - petstore_auth:
170
+ - write_pets
171
+ - read_pets
172
+ post:
173
+ tags:
174
+ - pet
175
+ summary: Updates a pet in the store with form data
176
+ description: ""
177
+ operationId: updatePetWithForm
178
+ consumes:
179
+ - application/x-www-form-urlencoded
180
+ produces:
181
+ - application/json
182
+ - application/xml
183
+ parameters:
184
+ - in: path
185
+ name: petId
186
+ description: ID of pet that needs to be updated
187
+ required: true
188
+ type: string
189
+ - in: formData
190
+ name: name
191
+ description: Updated name of the pet
192
+ required: true
193
+ type: string
194
+ - in: formData
195
+ name: status
196
+ description: Updated status of the pet
197
+ required: true
198
+ type: string
199
+ responses:
200
+ "405":
201
+ description: Invalid input
202
+ security:
203
+ - petstore_auth:
204
+ - write_pets
205
+ - read_pets
206
+ delete:
207
+ tags:
208
+ - pet
209
+ summary: Deletes a pet
210
+ description: ""
211
+ operationId: deletePet
212
+ produces:
213
+ - application/json
214
+ - application/xml
215
+ parameters:
216
+ - in: header
217
+ name: api_key
218
+ description: ""
219
+ required: true
220
+ type: string
221
+ - in: path
222
+ name: petId
223
+ description: Pet id to delete
224
+ required: true
225
+ type: integer
226
+ format: int64
227
+ responses:
228
+ "400":
229
+ description: Invalid pet value
230
+ security:
231
+ - petstore_auth:
232
+ - write_pets
233
+ - read_pets
234
+ /stores/order:
235
+ post:
236
+ tags:
237
+ - store
238
+ summary: Place an order for a pet
239
+ description: ""
240
+ operationId: placeOrder
241
+ produces:
242
+ - application/json
243
+ - application/xml
244
+ parameters:
245
+ - in: body
246
+ name: body
247
+ description: order placed for purchasing the pet
248
+ required: false
249
+ schema:
250
+ $ref: "#/definitions/Order"
251
+ responses:
252
+ "200":
253
+ description: successful operation
254
+ schema:
255
+ $ref: "#/definitions/Order"
256
+ "400":
257
+ description: Invalid Order
258
+ /stores/order/{orderId}:
259
+ get:
260
+ tags:
261
+ - store
262
+ summary: Find purchase order by ID
263
+ description: For valid response try integer IDs with value <= 5 or > 10. Other values will generated exceptions
264
+ operationId: getOrderById
265
+ produces:
266
+ - application/json
267
+ - application/xml
268
+ parameters:
269
+ - in: path
270
+ name: orderId
271
+ description: ID of pet that needs to be fetched
272
+ required: true
273
+ type: string
274
+ responses:
275
+ "404":
276
+ description: Order not found
277
+ "200":
278
+ description: successful operation
279
+ schema:
280
+ $ref: "#/definitions/Order"
281
+ "400":
282
+ description: Invalid ID supplied
283
+ delete:
284
+ tags:
285
+ - store
286
+ summary: Delete purchase order by ID
287
+ description: For valid response try integer IDs with value < 1000. Anything above 1000 or nonintegers will generate API errors
288
+ operationId: deleteOrder
289
+ produces:
290
+ - application/json
291
+ - application/xml
292
+ parameters:
293
+ - in: path
294
+ name: orderId
295
+ description: ID of the order that needs to be deleted
296
+ required: true
297
+ type: string
298
+ responses:
299
+ "404":
300
+ description: Order not found
301
+ "400":
302
+ description: Invalid ID supplied
303
+ /users:
304
+ post:
305
+ tags:
306
+ - user
307
+ summary: Create user
308
+ description: This can only be done by the logged in user.
309
+ operationId: createUser
310
+ produces:
311
+ - application/json
312
+ - application/xml
313
+ parameters:
314
+ - in: body
315
+ name: body
316
+ description: Created user object
317
+ required: false
318
+ schema:
319
+ $ref: "#/definitions/User"
320
+ responses:
321
+ default:
322
+ description: successful operation
323
+ /users/createWithArray:
324
+ post:
325
+ tags:
326
+ - user
327
+ summary: Creates list of users with given input array
328
+ description: ""
329
+ operationId: createUsersWithArrayInput
330
+ produces:
331
+ - application/json
332
+ - application/xml
333
+ parameters:
334
+ - in: body
335
+ name: body
336
+ description: List of user object
337
+ required: false
338
+ schema:
339
+ type: array
340
+ items:
341
+ $ref: "#/definitions/User"
342
+ responses:
343
+ default:
344
+ description: successful operation
345
+ /users/createWithList:
346
+ post:
347
+ tags:
348
+ - user
349
+ summary: Creates list of users with given input array
350
+ description: ""
351
+ operationId: createUsersWithListInput
352
+ produces:
353
+ - application/json
354
+ - application/xml
355
+ parameters:
356
+ - in: body
357
+ name: body
358
+ description: List of user object
359
+ required: false
360
+ schema:
361
+ type: array
362
+ items:
363
+ $ref: "#/definitions/User"
364
+ responses:
365
+ default:
366
+ description: successful operation
367
+ /users/login:
368
+ get:
369
+ tags:
370
+ - user
371
+ summary: Logs user into the system
372
+ description: ""
373
+ operationId: loginUser
374
+ produces:
375
+ - application/json
376
+ - application/xml
377
+ parameters:
378
+ - in: query
379
+ name: username
380
+ description: The user name for login
381
+ required: false
382
+ type: string
383
+ - in: query
384
+ name: password
385
+ description: The password for login in clear text
386
+ required: false
387
+ type: string
388
+ responses:
389
+ "200":
390
+ description: successful operation
391
+ schema:
392
+ type: string
393
+ "400":
394
+ description: Invalid username/password supplied
395
+ /users/logout:
396
+ get:
397
+ tags:
398
+ - user
399
+ summary: Logs out current logged in user session
400
+ description: ""
401
+ operationId: logoutUser
402
+ produces:
403
+ - application/json
404
+ - application/xml
405
+ responses:
406
+ default:
407
+ description: successful operation
408
+ /users/{username}:
409
+ get:
410
+ tags:
411
+ - user
412
+ summary: Get user by user name
413
+ description: ""
414
+ operationId: getUserByName
415
+ produces:
416
+ - application/json
417
+ - application/xml
418
+ parameters:
419
+ - in: path
420
+ name: username
421
+ description: The name that needs to be fetched. Use user1 for testing.
422
+ required: true
423
+ type: string
424
+ responses:
425
+ "404":
426
+ description: User not found
427
+ "200":
428
+ description: successful operation
429
+ schema:
430
+ $ref: "#/definitions/User"
431
+ "400":
432
+ description: Invalid username supplied
433
+ put:
434
+ tags:
435
+ - user
436
+ summary: Updated user
437
+ description: This can only be done by the logged in user.
438
+ operationId: updateUser
439
+ produces:
440
+ - application/json
441
+ - application/xml
442
+ parameters:
443
+ - in: path
444
+ name: username
445
+ description: name that need to be deleted
446
+ required: true
447
+ type: string
448
+ - in: body
449
+ name: body
450
+ description: Updated user object
451
+ required: false
452
+ schema:
453
+ $ref: "#/definitions/User"
454
+ responses:
455
+ "404":
456
+ description: User not found
457
+ "400":
458
+ description: Invalid user supplied
459
+ delete:
460
+ tags:
461
+ - user
462
+ summary: Delete user
463
+ description: This can only be done by the logged in user.
464
+ operationId: deleteUser
465
+ produces:
466
+ - application/json
467
+ - application/xml
468
+ parameters:
469
+ - in: path
470
+ name: username
471
+ description: The name that needs to be deleted
472
+ required: true
473
+ type: string
474
+ responses:
475
+ "404":
476
+ description: User not found
477
+ "400":
478
+ description: Invalid username supplied
479
+ securityDefinitions:
480
+ api_key:
481
+ type: apiKey
482
+ name: api_key
483
+ in: header
484
+ petstore_auth:
485
+ type: oauth2
486
+ authorizationUrl: http://petstore.swagger.io/api/oauth/dialog
487
+ flow: implicit
488
+ scopes:
489
+ write_pets: modify pets in your account
490
+ read_pets: read your pets
491
+ definitions:
492
+ User:
493
+ type: object
494
+ properties:
495
+ id:
496
+ type: integer
497
+ format: int64
7
498
  username:
8
- validations: Debe tener un numero por que si
9
- type: String
10
- password:
11
- validations: Tiene que ser 1234
12
- type: String
499
+ type: string
500
+ firstName:
501
+ type: string
502
+ lastName:
503
+ type: string
13
504
  email:
14
- validations: Debe ser de google
15
- type: String
16
- optional_parameters:
17
- aficiones:
18
- validations: Debe contener 300 caracteres como minimo
19
- type: String
20
- example_data:
21
- username: supertomate@gmail.com
22
- password: supertomate@gmail.com
23
- aficiones: supertomate@gmail.com
24
- email: supertomate@gmail.com
25
- headers:
26
- content_type: application/json
27
- accept: application/json
28
- method: put
29
- description: Modificar un usuario
30
- path: "/users"
31
- description: Esta es la seccion dedicada a las rutas de usuario. El usuario es cada una de las personas o entes que tienen acceso a una o varias empresas.
32
- title: Usuario v1
505
+ type: string
506
+ password:
507
+ type: string
508
+ phone:
509
+ type: string
510
+ userStatus:
511
+ type: integer
512
+ format: int32
513
+ description: User Status
514
+ Category:
515
+ type: object
516
+ properties:
517
+ id:
518
+ type: integer
519
+ format: int64
520
+ name:
521
+ type: string
522
+ Pet:
523
+ type: object
524
+ required:
525
+ - name
526
+ - photoUrls
527
+ properties:
528
+ id:
529
+ type: integer
530
+ format: int64
531
+ category:
532
+ $ref: "#/definitions/Category"
533
+ name:
534
+ type: string
535
+ example: doggie
536
+ photoUrls:
537
+ type: array
538
+ items:
539
+ type: string
540
+ tags:
541
+ type: array
542
+ items:
543
+ $ref: "#/definitions/Tag"
544
+ status:
545
+ type: string
546
+ description: pet status in the store
547
+ Tag:
548
+ type: object
549
+ properties:
550
+ id:
551
+ type: integer
552
+ format: int64
553
+ name:
554
+ type: string
555
+ Order:
556
+ type: object
557
+ properties:
558
+ id:
559
+ type: integer
560
+ format: int64
561
+ petId:
562
+ type: integer
563
+ format: int64
564
+ quantity:
565
+ type: integer
566
+ format: int32
567
+ shipDate:
568
+ type: string
569
+ format: date-time
570
+ status:
571
+ type: string
572
+ description: Order Status
573
+ complete:
574
+ type: boolean