Sometime in the new year.  Please follow https://twitter.com/OpenApiSpec 
<https://twitter.com/OpenApiSpec> for notifications on it.

> On Nov 29, 2016, at 3:56 AM, rkushnir <[email protected]> wrote:
> 
> Hi, when should the next version be released? Do you know already?
> 
> Thanks
> 
> On Thursday, November 10, 2016 at 6:26:47 PM UTC+2, Ron wrote:
> The next version of the spec (not released yet) already has support for this.
> 
>  
>  
>  
> From: <[email protected] <javascript:>> on behalf of Guillermo 
> Martínez del Camino <[email protected] <javascript:>>
> Reply-To: "[email protected] <javascript:>" 
> <[email protected] <javascript:>>
> Date: Thursday, 10 November 2016 at 2:15
> To: Swagger <[email protected] <javascript:>>
> Subject: Re: How to handle choice in Swagger 2.0
> 
>  
> I am rescuing this topic as I believe adding choice would be great for the 
> swagger spec. We have got, for instance, an IP that queries billing events. 
> Such events could be calls, SMSs, data traffic, or digital assets such as a 
> movie download. They have a common part (the ID, time, etc.) and a specific 
> part depending on the event type. We are having trouble documenting it as 
> Swagger today cannot cope with the requirement. My proposal would be to add 
> it this way:
> 
>  
> "properties": [{
> 
>  
>     ...
> 
>  
>     "element": {
> 
>         "type": "choice",
> 
>         "choices": [{
> 
>             "$ref": "#/definitions/possibleType1"
> 
>         },
> 
>         {
> 
>             "$ref": "#/definitions/possibleType2"
> 
>         },
> 
>         {
> 
>             "type": "string"
> 
>         }]
> 
>     }
> 
>  
> ...
> 
>  
> }]
> 
>  
> Same way an array has its "items" field or a string has its "enum" or format 
> field, choice would have an array of possible choices which would contain 
> either a type or a reference.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Swagger" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Swagger" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to