Do we need to revisit the pagination cursors? about lighthouse HOT 3 CLOSED

@hailwood Love this! Didn't even notice the new forPageAfterId but it sounds like a pretty solid drop in replacement. I also really like the encode/decode functionality you're proposing here... so if someone wanted to base it off a different column (such as a timestamp) they could, we would just need to allow them to override the column name in their connection class.

I'll try to add in this functionality by next week unless you wanted to submit a PR.

Thanks!!

from lighthouse.

@hailwood Actually, I don't think forPageAfterId would necessarily work. Primarily because it's not a LengthAwarePaginator so we don't have things like the total count. It also looks like we might run into issues when trying to sort desc or if we have a sort on a different field coming from an argument in the resolver. I'll look into the issues you're experiencing and see if I can find out what's going on, but in the meantime it seems like it would still be beneficial to move from a trait to a Relationship macro.

from lighthouse.

Fixed via #65

from lighthouse.