Features
- API versions can be expressed using conventions
- HTTP 400 responses related to API versioning can be customized (not recommended)
Bugs Fixed
- OData Controller Should Return 400 Instead of 404 (#17)
- ApiVersionRouteConstraint Always Returns False for Url Generation (#19)
- ASP.NET Core Controller Should Return 400 Instead of 404 (#20)
- API Version 400 Responses are Not Compliant by Default (#25)
- Convention-Based Action Routes Do Not Return 400 as Expected (#26)
- URL Segment Versioned Controllers Do Not Report All API Versions (#27)
Breaking Changes
- API version URL segements specified in the prefix for OData routes now use the same route constraint as other ASP.NET Web API routes; however, the route constraint name cannot be changed. The route contraint name must exactly be defined as {apiVersion}; for example, api/v{apiVersion}.