Code in https://aspnetwebstack.codeplex.com/SourceControl/latest#src/System.Web.Http/Description/ApiExplorer.cs removes all duplicates based on HTTP method + path
This is not sometimes the desired logic.
Can we implement a injectable ApiDescriptionComparer so the consumer of the ApiExplorer can control what duplicates are removed and what are needed.
Comments: Sample project attached and here's a quick summary. (__Note:__ Sample uses rc1 bits from official nuget server but same happens with nightly builds) Our web application is simply a host which hosts Api content in separate plugin assemblies. All controllers, logic and models are contained within these assemblies. The v2 content is essentially a clone and extension of the v1 content. This allows us to modify and evolve v2 while still maintaining a snapshot of the v1 content for backwards compatibility. However you'll notice that when navigating to the help page that because of the issues called out above that the ApiExplorer throws away some of the ApiDescriptions erroneously. Especially so because the models that v1 and v2 return are different. Hopefully this makes sense. Thanks for looking at this. ~Derek
This is not sometimes the desired logic.
Can we implement a injectable ApiDescriptionComparer so the consumer of the ApiExplorer can control what duplicates are removed and what are needed.
Comments: Sample project attached and here's a quick summary. (__Note:__ Sample uses rc1 bits from official nuget server but same happens with nightly builds) Our web application is simply a host which hosts Api content in separate plugin assemblies. All controllers, logic and models are contained within these assemblies. The v2 content is essentially a clone and extension of the v1 content. This allows us to modify and evolve v2 while still maintaining a snapshot of the v1 content for backwards compatibility. However you'll notice that when navigating to the help page that because of the issues called out above that the ApiExplorer throws away some of the ApiDescriptions erroneously. Especially so because the models that v1 and v2 return are different. Hopefully this makes sense. Thanks for looking at this. ~Derek