The problem is not caching, the problem is that the filter doesn’t let you manipulate content of the spec – it just lets you filter out specific things (operations, paramters…).
The ApiListingResource gives you access to the Swagger object itself, which you can manipulate with whatever logic you want. From: <swagger-swaggersocket@googlegroups.com> on behalf of Bryan Nelson <bryan.j.nel...@gmail.com> Reply-To: "swagger-swaggersocket@googlegroups.com" <swagger-swaggersocket@googlegroups.com> Date: Wednesday, 21 June 2017 at 6:03 To: Swagger <swagger-swaggersocket@googlegroups.com> Subject: Re: Swagger-Core - Caching of Tag Data in Operations? I've looked back over that previous thread, but I don't follow you. I understand how to extend ApiListingResource, but I don't understand how that would help me. How would that help me with the caching issue? Could you elaborate a bit? Thanks. -- 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. -- 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.
