Change Details

'after' argument in pagination is confusing and will cause issues with relay, It will return objects from 'after' cursor. This is not in sync with the behavior of other popular GraphQL services. Fix the same issue in pagination in the GraphQL layer as well. (utils.paginated function)

Fix issue in pagination 'after' argument - Add missing mandatory fields to pageinfo - after argument fix It will return objects from 'after' cursor. This is not in sync with the spec

'after' argument in pagination is confusing and will cause issues with relay, It will return objects from 'after' cursor. This is not in sync with the behavior of other popular GraphQL services.Fix issue in pagination 'after' argument Fix the same issue in pagination in the GraphQL layer as well. (utils.paginated function)- Add missing mandatory fields to pageinfo - after argument fix It will return objects from 'after' cursor. This is not in sync with the spec