fix: cursor connection issue with orderBy

[limitless-dev]

Description

The issue occurred when using the orderBy argument in the publishedPosts query. If an orderBy field was specified (other than id), and a cursor-based pagination was used with first and after parameters, the cursor connection could become broken. This resulted in inaccurate pagination results

Solution

• Include an additional ordering by id in the Prisma query by appending { id: 'desc' } as a secondary order in the orderBy array.

Note

This may need to be adapted based on your specific implementation and requirements.