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/adr/0000-subresources-definition.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ We choose to use multiple `ApiResource` annotations to declare subresources on a
19
19
20
20
* Subresource declaration is an important feature and removing it would harm the software.
21
21
* The `ApiSubresource` annotation is declared on a Model's properties, which was identified as the root of several issues. For example, finding what class it is defined on ([#3458][issue/3458]). Having multiple `ApiResource` would improve a lot the declaration of our internal metadata and would cause less confusion for developers.
22
-
* The `path` of these multiple `ApiResource` needs to be implicitly described.
22
+
* The `path` of these multiple `ApiResource` needs to be explicitly described.
23
23
* An `ApiResource` is always defined on the Resource it represents: `/companies/1/users` outputs Users and should be defined on the `User` model.
24
24
* PropertyInfo and Doctrine metadata can be used to define how is the Resource identified according to the given path.
0 commit comments