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
Copy file name to clipboardExpand all lines: docs/usage/extensibility/controllers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,10 +126,10 @@ You can even make your own mix of allowed routes by calling the alternate constr
126
126
In some cases, resources may be an aggregation of entities or a view on top of the underlying entities. In these cases, there may not be a writable `IResourceService` implementation, so simply inject the implementation that is available.
In v4.0 we introduced an extension method that you can use to register a resource repository on all of its JsonApiDotNetCore interfaces.
@@ -26,7 +26,7 @@ A sample implementation that performs authorization might look like this.
26
26
All of the methods in EntityFrameworkCoreRepository will use the `GetAll()` method to get the `DbSet<TResource>`, so this is a good method to apply filters such as user or tenant authorization.
@@ -41,7 +41,7 @@ For example, you may accept some sensitive data that should only be exposed to a
41
41
>Toexcludefieldsunconditionally, [attributecapabilities](~/usage/resources/attributes.md#capabilities) and [relationshipcapabilities](~/usage/resources/relationships.md#capabilities) canbeusedinstead.
In v3.0 we introduced an extension method that you can use to register a resource service on all of its JsonApiDotNetCore interfaces.
@@ -149,11 +149,11 @@ public class Article : identifiable<long>
149
149
Alternatively, when using a hand-written controller, you should inherit from the JSON:API controller and pass the services into the named, optional base parameters:
0 commit comments