CommentsViewTerms not respected in GraphQL

[jeffkaufman]

If I use the graphql interface and send:

{
  posts(input: {terms: {limit: 3, after: "2021-01-01", before: "2022-01-01"}}){
    results {
      postedAt
    }
  }
}

I get three dates from 2021, as you'd expect.

If instead I send:

{
  comments(input: {terms: {limit: 3, after: "2021-01-01", before: "2022-01-01"}}){
    results {
      postedAt
    }
  }
}

I instead get three dates from today.

I've also tried using postId and a few other values from CommentsViewTerms, but none of them seem to have any effect.

┆Issue is synchronized with this Asana task by Unito

[jeffkaufman]

After looking at how my comment fetcher works, I was able to get postId to work by adding view: "postCommentsOld":

{
  comments(input: {terms: {view: "postCommentsOld", postId: "H6hxTrgFpb3mzMPfz", limit: 3}}){
    results {
      postId
    }
  }
}

Gives postId H6hxTrgFpb3mzMPfz three times, while:

{
  comments(input: {terms: {postId: "H6hxTrgFpb3mzMPfz", limit: 3}}){
    results {
      postId
    }
  }
}

Gives three other postIds.

[jeffkaufman]

But before/after still don't do anything:

{
  comments(input: {terms: {view: "postCommentsOld", after: "2021-01-01", before: "2022-01-01", limit: 3}}){
    results {
      postId
      postedAt
    }
  }
}

Gives three comments from 2013.

[jpaddison3]

Sadly, the API is much less fully-featured than you think. terms can take whatever we want it to, and we built before/after into the post views, but haven't needed it in the comments views. You could imagine that there's some higher-level place to do that logic, but nothing like that has been built.