THANK YOU! I'm VERY happy of what you taught me - albeit embarrassed. I now realize that I misinterpreted the meaning behind the Path @ref specs "Allows for an *external* definition of this path item. "
I actually had encountered these seemingly weird ~0 and ~1 "escapes" in my readings, but never recognized them as anything related to JavaScript, XML, URI or other familiar escaping schemes, or at least anything intuitive - and thus it never really sank in. But thanks to your practical example, I finally perused the JSON specs on pointers (https://tools.ietf.org/html/rfc6901#page-3) - and I finally appreciate the necessity of escaping these two characters when used in pointers. This solves my application problem! On Thursday, November 9, 2017 at 7:16:08 PM UTC-5, Ron wrote: > Out of the three statements, only b) is true. > > > > The spec does allow internal references. > > > > Your first reference sample is mostly valid, only it needs to be escaped: > $ref: "#/paths/~1request1". > > You can technically also contain Path Items Objects in an extension and > reference those locally. > > > -- 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.
