Is your feature request related to a problem? Please describe.
The current events provide behavior like UserBehaviorTrait. These methods only return an array (if the value is available). It would be nice if these arrays were wrapped in a proper VO.
Describe the solution you'd like
Wrap the user key in a User VO. Same for commit, object_attributes, project and repository.
Additional context
It's way easier to deduce which data is available on the object in question if a value object provides those getters. Like User::getUsername(). Instead of having to check for username on the array.
Is your feature request related to a problem? Please describe.
The current events provide behavior like
UserBehaviorTrait. These methods only return an array (if the value is available). It would be nice if these arrays were wrapped in a proper VO.Describe the solution you'd like
Wrap the
userkey in aUserVO. Same forcommit,object_attributes,projectandrepository.Additional context
It's way easier to deduce which data is available on the object in question if a value object provides those getters. Like
User::getUsername(). Instead of having to check forusernameon the array.