Skip to main content

ISSUE_COMMENTS

Constant ISSUE_COMMENTS 

Source
pub const ISSUE_COMMENTS: &str = "query($id:ID!,$first:Int!,$after:String){node(id:$id){__typename ... on Issue{comments(first:$first,after:$after){nodes{id author{login} createdAt updatedAt body url}pageInfo{hasNextPage endCursor}}}}}";
Expand description

One task’s comments: a page of its issue’s own comments connection.

No orderBy, and that is what makes the page oldest first. GitHub’s only IssueCommentOrder field is UPDATED_AT, which would move a comment to the end of the list every time somebody edited it; left unordered the connection answers in the order the comments were written, which is the order GitHub documents for the same collection over REST — ascending id. Nothing multiplies through it, so $first is the whole of its node count and the caller’s own page size is pushed straight down.