Contributions
dependency to spring-plugin-core 1.2.0
Hello The maven project generated by codegen (server stub & spring boot) has a dependency to spring-plugin-core 1.2.0 (as shown in the effective POM in Eclipse). However I cannot find one single dependecy in the maven pom tha tpoints to this release of the plug in This is bad a 2.0.0 is needed. Otherwise the microservice simply fails Can someone help me with this? Regards Christophe589Views0likes1Commentdependency to spring-plugin.version 1.2.0.RELEASE
Hello I am facing the following strange situation I use swagger hub to specify apis and codegen for spring boot to generate the server stubs and maven POM This POM creates a dependency tospring-plugin.version 1.2.0.RELEASE wich I can find nowhere in the dependencies. It looks like it conflicts (at lest this is what eclipse displays) withspring-plugin.version 2.0.0.RELEASE When the jar is generated & repackaged the wrong verion of th eplugin is inserted in the resulting jar (1.2.0 instead of 2.0.0) and of course the microservice fails to start. I have tried for hours to find ou where this dependency came from (as the maven tools I ran do not find it) Can someone help me with this? Regards Christophe398Views0likes0CommentsSwager codegen for spring boot: how is swagger-ui page generated
Hello I was wondering how theswagger-ui page was generated, mostly how the various annotations where used to build the page. I am facing a fairly large number of defects (at least I beleive these are defects) and if I could find y way around the HTML generation it certainly would help me either pinpoint a defect somewhere or understnd what I do not do right One of my issues is that the nullable properties of fields in output aggregates is ignored. The other is the errors displayed by the page when an aggregate is diffined as an arrau opt-out-flags: type: array items: $ref: '#/components/schemas/opt-out-media' Spring doc (or is it spring fox) displays a error Any pointer is welcome Regards Christophe744Views0likes1Commentissue with nullable fields
Hello I use swagger to define APIS, their input and output parameters In the case of Output parameters I define the following agregate in a domain : schemas: account-token: type: object properties: k0: type: string nullable: true k1: type: string nullable: true status: type: string nullable: true As you can see all 3 fields are nullable. However the code generated by the code gen (for spring boot 2.1.7) ignores this property. Furthermore evben if I add this annotation @Schema(nullable=true) the nullable natude of those fields is ignored Is there something I do not do righ? Is it a bug? Can someone give me pointers? Regards Christsophe488Views0likes0Comments