Releases · Adrinalin4ik/Nestjs-Graphql-Tools

// users-application/src/users/users.resolver.ts
@ResolveReference()
@GraphqlLoader()
async resolveReference(
   @Loader() loader: LoaderData<User, number>,
) {
 const ids = loader.ids;
 const users = this.usersService.findByIds(ids);
 return loader.helpers.mapManyToOneRelation(users, loader.ids, 'id')
}

Add method findByIds to users-application/src/users/users.service.ts

// users-application/src/users/users.service.ts
@Injectable()
export class UsersService {
  private users: User[] = [
    { id: 1, name: 'John Doe' },
    { id: 2, name: 'Richard Roe' },
  ];

  findByIds(idsList: number[]): User[] {
    return this.users.filter((user) => idsList.some(id => Number(id) === user.id));
  }
}

Install dependencies of 3 projects : npm ci in gateway, posts-application, users-application.
Run all projects in order :
- cd users-application && npm run start
- cd posts-application && npm run start
- cd gateway && npm run start
Go to localhost:3001/graphql and send graphql request to gateway

{
  posts {
    id
    title
    authorId
    user {
      id
      name
    }
  }
}

Assets 2

04 Sep 16:34

Adrinalin4ik

0.8.0

7a67dfc

Version 0.8.0

Updated deps
@GraphqlFilter and @GraphqlSorting method decorators are no longer required and marked as deprecated. These decorators will be removed soon.
@filter decorator now has it's own type FilterArgs. It should be used insted of Brackets in all the cases.
Fixed problem related to global pipes like ValidationPipe. This problem happened because pipe created dummy model based on types provided for the @filter decorator (it was typeorm Brakets). Please use FilterArgs type insted of Brackets to avoid this bug.