Include and filter by properties in nested relations

Hi,

I’m trying to get relations to work with nested relations. Let’s say I have entities A, B, and C. A has a Many-to-One to B, and B has a One-to-One to C. If I am using the pagination on A, but trying to filter by values on C, it looks like I can’t. relations option seems to only accept “surface” relations, and I’ve been trying to build a custom query builder but even if I can manage to include these relations, filtering seems to still be broken.

Am I missing something? Thanks.

[emrivero]

@FlyingOddo @ppetzold Hey! Apologies for forgetting to do the PR. As I had to make some more changes I have to check that the tests are passing I will do it as soon as possible.

[thegriglat]

Hi all, it seems I found a workaround for nested relations

The main idea is to use custom queryBuilder which will mask needed relation as core entity’s relation

Assume the following relations between entities: User -> Photos -> Comments and we need to filter by comments.likes property. When we will use comments.likes in filter or searchBy query – nestjs-paginate will try to find user.comments property in user_comments table name – and use our manual left join! PROFIT!

Snipper to illustrate the idea (at least smth like that works in my project):

const qb = this.userRepository
      .createQueryBuilder('user')
      .leftJoinAndSelect('user.photos', 'user_photos')
      // fake user.photos.comments relation, so paginate will assume that comments is user's property
      .leftJoinAndSelect('user_photos.comments', 'user_comments')

    await paginate<User>(request, qb, {
      relations: ['photos'],
      filterableColumns: {
        // use comments.likes as paginate will append `user_` prefix and will use left join above
        'comments.likes': [FilterOperator.EQ, FilterOperator.NOT, FilterOperator.IN],
        // any needed here as comments.likes isn't user property and otherwise will break TS types
      } as any,
    })