Weird behaviour of paging

[akaNightmare]

Hello,

import { GQC } from 'graphql-compose';
import composeWithPagination from 'graphql-compose-pagination';
import userTypeComposer from '../modules/user/types';

GQC.rootQuery().addFields({
    userById: userTypeComposer.getResolver('findById'),
    userOne: userTypeComposer.getResolver('findOne'),
    userMany: userTypeComposer.getResolver('findMany'),
    userCount: userTypeComposer.getResolver('count'),
    userPagination: userTypeComposer.getResolver('pagination'),
});

GQC.rootMutation().addFields({
    userCreate: userTypeComposer.getResolver('createOne'),
});

composeWithPagination(userTypeComposer, {
    findResolverName: 'findMany',
    countResolverName: 'userCount',
});

export default GQC.buildSchema();

GraphQL Query

{
  users: userPagination {
    items {
      name
    }
    pageInfo {
      currentPage
      pageCount
      perPage
      itemCount
    }
  }
}

LOG:
[1] Mongoose: users.find({}, { limit: 21, fields: { items: true, pageInfo: true, name: true } })

I think Items and pageInfo are unnecessary in fields object.

[nodkz]

The same behavior exists in connection. It's done for better wrapping your resolvers, all top level projections pass down to find method.

I do not have a suitable example at hand right now. But really was problems when I do not pass top level projection when constructing complex relations between types. So for removing this fields needs to improve projection logic when constructing relations.

In future, it may be fixed, but for now it, not such big problem on which I want to spend my time.

[akaNightmare]

Thanks, let's keep it open.