You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rewrite of LinkBuilder to use ASP.NET Core routing to render links (#987)
Rewrite of LinkBuilder to use ASP.NET Core routing to render links. The limitation that custom routes must end in the public resource name no longer applies.
- Fixed: Resource-level Self links in atomic:operations responses are now hidden when no controller exists for the resource type.
- Fixed: For determining which links to render, settings from primary resource were used on secondary endpoints. For example, if you configure Customer to show all links, but Orders no show none, then /customer/1/orders would show all links.
- Optimization: Compound `page[size]` parameter value (example: `10,articles:5`) is calculated once, instead of again for each pagination link.
- Deprecated: `IJsonApiRequest.BasePath`. This information is no longer needed, but we still set it for back-compat.
- Added support for non-standard route parameters in links, for example: `[DisableRoutingConvention, Route("{shopName}/products")]`
@@ -73,8 +73,6 @@ public class OrderLineController : JsonApiController<OrderLine>
73
73
}
74
74
```
75
75
76
-
It is required to match your custom url with the exposed name of the associated resource.
77
-
78
76
## Advanced Usage: Custom Routing Convention
79
77
80
78
It is possible to replace the built-in routing convention with a [custom routing convention](https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/application-model?view=aspnetcore-3.1#sample-custom-routing-convention) by registering an implementation of `IJsonApiRoutingConvention`.
0 commit comments