Allows for building subroles in an explicit manner.
Discussion
Currently, roles and subroles coexist and are used interchangeably, as
instances of the Role data model. This is very confusing, as the only thing
they have in common is the key attribute, shared with every other data model
in the entities module. By declaring SubRole as an independent data model
from Role, we can make the distinction between the two clearer, improving
readability, maintenance, debugging, and eventual extensibility of both.
coverage: 73.695% (+0.2%) from 73.501% when pulling c78940ace2f055488331ed7e5955282d8cd6309c on compose-entity-2 into a3c2f8324d5b139c3fbf2b0b9190c630661af66c on master.
Depends on #1197
New features
SubRole
.Discussion
Currently, roles and subroles coexist and are used interchangeably, as instances of the
Role
data model. This is very confusing, as the only thing they have in common is thekey
attribute, shared with every other data model in theentities
module. By declaringSubRole
as an independent data model fromRole
, we can make the distinction between the two clearer, improving readability, maintenance, debugging, and eventual extensibility of both.