Re: codegen of $ref JSON pointer references

Great, thanks for the follow-up > On Oct 27, 2016, at 10:50 PM, Lex Luthra wrote: > > Hi Tony, > > I can confirm the issue has been fixed on master: 31b32a8 - Merge pull > request #4094 from swagger-api/issue-4090 > > Thanks, > Alex > > > On Friday, 28 October 2016 14:20:55 UTC+11, tony tam

Re: codegen of $ref JSON pointer references

Hi Tony, I can confirm the issue has been fixed on master: 31b32a8 - Merge pull request #4094 from swagger-api/issue-4090 Thanks, Alex On Friday, 28 October 2016 14:20:55 UTC+11, tony tam wrote: > > Hi Lex, please pull master and test it. A major update was pushed today > to the swagger-pars

Re: codegen of $ref JSON pointer references

Hi Lex, please pull master and test it. A major update was pushed today to the swagger-parser which addresses the relative references that you seem to have in your doc. https://github.com/swagger-api/swagger-codegen/pull/4094 > On Oct

Re: codegen of $ref JSON pointer references

Hi Tony, I am attaching a standalone test harness that can be used to test the said issue (codegen not generating *all* Java classes for some JSON pointer references in the spec). Cheers, Lex. On Tuesday, 25 October 2016 15:41:46 UTC+11, tony tam wrote: > > Hi Lex, > If you could please share

Re: codegen of $ref JSON pointer references

Hi Lex, If you could please share some details of your structure, we can look at it. There are a couple known issues with swagger-parser (the underlying parse/resolve utility for codegen) that are being worked on right now. If you have additional test cases, I’d love to get them in. See here:

codegen of $ref JSON pointer references

I recently created a new OpenAPI project using YAML and generated a client using codegen module. As per some of the advice on this and other forums, I subsequently split my spec into several files and used JSON pointer references to link them. However, I noticed that when using codegen to gener