AttributeRouteStrategy ignores ODataRoutePrefix when generating the path template

[jalstrup]

We are running into an issue with the path templates not being generated correctly when using an ODataRoutePrefix. Our OData endpoint is set up in the following way.

Config

config.MapODataServiceRoute("AdminOData", "api/v1/admin", ODataEdmModelProvider.GetEdmModel());

Controller

    [ODataRoutePrefix("products")]
    public class ProductsController : ODataController
    {
        [EnableQuery]
        [ODataRoute("({key})/attributevalues({attributevalueKey})")]
        public IHttpActionResult GetAttributeValue(Guid key, Guid attributevalueKey)
        {
            return this.Ok();
        }
    }

It looks like the ODataActionDescriptor is created by the AttributeRouteStrategy. To generate the path template it looks like it is using the ODataRoute prefix (in this scenario "api/v1/admin") and ODataRouteAttribute.PathTemplate (in this scenario "({key})/attributevalues({attributevalueKey})") to generate the path template. The resulting path template ends up looking like the following.

api/v1/admin/({key})/attributevalues({attributevalueKey})

I would expect it to be

api/v1/admin/products({key})/attributevalues({attributevalueKey})

I think the same logic that is being used by AttributeRoutingConvention.GetODataPathTemplate would be needed to generate the correct path.

[rbeauchamp]

Hey @jalstrup, thanks for posting this issue. I'll look into it.

[mjolka]

@rbeauchamp I've created a branch that hopefully fixes this problem. Please let me know if you have any feedback, or would be willing to merge.

[rbeauchamp]

@mjolka Thank you! Please submit a pull request and I'll check it out.

[ghost]

Fixed by #84.

[ghost]

Fix is available in v2.18.0