6d0b7af54e
We use Spring's native support for projections here, instead of setting the `.fields()` ourselves. The advantage is that this way translates directly to Postgres. The cost is that, the field names in projection are duplicated. For example, if `profilePhotoAssetId` is renamed or otherwise changed, we won't see a compile error. This can be prevented with a test. The `findPhotoAssetsByUserIds_WhenPhotoAssetIdExist_ReturnsPhotoAssetId` test is able to catch this case perfectly well. |
||
|---|---|---|
| .. | ||
| client | ||
| server | ||
| util | ||