Yeah that doesn't seem like a bad approach. The whold point of the serializer is to know how to translate a domain object into a basic data type for response. So if a `User` response is not valid without the skills arrays serializing a `User` should also serialize its value objects/composed properties, IMO. Thus, injecting a SkillArraySerializer is one way you could accomplish that goal.

It has the benefit that it's miles better than having to handle this logic in the client code.