I think you’re describing that a value can be “null” or an “object”, forgetting specification semantics. That would be done with the “required” flag unless I’m misunderstanding something thing.
> On Dec 2, 2016, at 9:13 AM, Daniel Popowich <danielpopow...@gmail.com> wrote: > > > > On Friday, December 2, 2016 at 12:05:24 PM UTC-5, tony tam wrote: > Hi, we are adding the oneOf and anyOf support in 3.0, and I believe the > “nullable” support is being added as well. > > In other words, there's no way in 2.0 to specify a property of an object may > be either NULL or a $ref? > > > > -- > 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 swagger-swaggersocket+unsubscr...@googlegroups.com > <mailto:swagger-swaggersocket+unsubscr...@googlegroups.com>. > 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 swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
