I've filed a bug report for this here: https://github.com/swagger-api/swagger-parser/issues/302
I've also discovered that if you move back to swagger parser 1.0.21 that this functionality works, but a different problem is broken... On Tuesday, September 20, 2016 at 2:36:40 PM UTC-4, Brent Ryan wrote: > > Using the swagger definition below with 2.3.0-SNAPSHOT (latest) doesn't > seem to work with "importMappings" in all cases. The reason for this is > the SwaggerParser tries to resolve the references and it can't find > FooType. However, this works sometimes and I can't figure out why... > > Also, what is the expected way to reference an external type? If I have a > class at com.foo.FooType and I've defined my "import-mappings" as > FooType=com.foo.FooType I want swagger to ignore resolving this reference > and just include the import in the generated code. > > type: object > description: Schema for defining foo > properties: > fooType: > description: foo settings > $ref: '#/definitions/FooType' > > > Should it be this? This doesn't work either. > > type: object > description: Schema for defining foo > properties: > fooType: > description: foo settings > type: 'FooType' > > If you have a type like this then it works for some reason and I suspect > it's because the swagger parser doesn't resolve references properly for > collections like this: > > type: object > description: Schema for defining foo > properties: > fooType: > type: array > items: > $ref: '#/definitions/FooType' > > Any thoughts? What's wrong here? > > -- 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.
