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
My opinion: I don't think we need to express these any differently. Container resource should still have standard fields: they will just be fairly bare-bones.
One reason is that even with a resource that only contains other resources, it still needs an id, and likely additional CRUDL operations to operate on them.
If there's a special property that makes them differ from a fundamental resource, then I think there's a good motivation to specify them.
Context: https://github.com/aep-dev/aepc/pull/1/files#r1332008974
There are resources that are more or less containers of other resources, rather than have any behavior in it's own right.
The question is: should these be expressed in the resource model via some specific property?
The text was updated successfully, but these errors were encountered: