Ability to configure Conventions in a non-generic way

[dotnet]

Ability to configure Conventions in a non-generic way

[commonsensesoftware]

Succinctly, I'll say that out-of-the-box - no. Individual services (e.g. controllers) require that API versioning be explicit per controller. This is the only way to reliably ensure things map the right way. The only exception is the implicit matching for the default API version. This behavior, however, is primarily meant to support backward compatibly once you opt into API versioning. To keep things unambiguous, there can only be one use case that supports this behavior.

The underlying code does not explicitly reply on attributes or conventions. It's really looking for implementations of IApiVersionProvider. You can easily extend the built-in attributes or you can define your own attributes that implement this interface. The extensions and customizations topic describes how this can be done. You can also choose to inherit from ApiVersionsBaseAttribute and implement IApiVersionProvider. It may also be to achieve your goals using a custom IApiVersionSelector.

Hopefully, this helps and gets you on your way. Keep in mind that it's critical that when the library asks what versions a controller supports, this can be retrieved in an unambiguous way.

[Broodja]

Thanks for clarification! IApiVersionProvider should be an answer, even it's not as straightforward as I wish.