Open nohponex opened 8 years ago
An alternative name may be better, "CLASSES"
is confusing
How about ENTITY ?
How about ENTITY ?
We need something that shows that some resources of that type share common properties, i.e. the form a group or a class.
I would prefer class but it's confusing for the developers since we are working with OOP
Each resource model should define a method
bool isA(string $class, string $id, $resourceObject = null)
also each resource model should define zero or more classesliteral values of the classes can be constants
In this way we can have a standard method to check the definitions and the criteria for each resource's classes (and/or states).
The resource model is responsible to implement
isA
method in order to returntrue
orfalse
for each of the available classes.Examples: