Niko
12/13/2021, 11:00 AMdata class A { name: String, value: Int }
that is used by the internals of the library for calculations and what not.
In addition, I have Android client (and backend service in the future) that on top of the `A`'s fields would need to have some info, like database ID, timestamps etc.
Writing the queries, I'm given the generated projections for the queries, but what if I wanted for the returned types to extend the library type's field and functionalities?
Can the projections extend other types?
Or write a custom mapper
to return another type having both types via composition/delegation?
Or am I just over-thinking this issue, and would the projections just be enough (most of the time they would, if they were just stupid data containers for the UI, but for some calculations they wouldn't cut it)? If I wanted to avoid redundant code-duplication, extending would be fitting