Wrong algorithm for pageInfo.hasPreviousPage and pageInfo.hasNextPage?

[Hybrid-Force]

Thanks for the amazing library, first of all!

Please correct me if I am wrong, it seems that the algorithm for pageInfo.hasPreviousPage and pageInfo.hasNextPage fields are not following with the cursor connections spec.

graphql-compose-connection/src/connectionResolver.js

Lines 338 to 339 in 29269dd

	pageInfo.hasPreviousPage = (!!args.last || !args.first) && (skip > 0 || !!args.after);
	pageInfo.hasNextPage = (!!args.first || !args.last) && hasExtraRecords;

With current implementation, in forward pagination situation with first/after, pageInfo.hasPreviousPage is always set to false. And pageInfo.hasNextPage always false in backward pagination. In forward pagination, pageInfo.hasNextPage is only working with first and last both set, which is discouraged.

I am wondering if this deviation from the spec is intentional or is it a potential bug?

[nodkz]

It looks like a bug. Can you provide test case or send a pull request?

[Hybrid-Force]

It looks like a bug. Can you provide test case or send a pull request?

Sure, I will try put together a pull request.