The following GQL resolvers unexpectedly return true for hasPrevious / hasNext pages when given invalid or empty cursors. This is because the pagination logic determines these flag values by the existence of the cursor value, instead of inferring the existence of pages from the returned data.
- connectors
- dataPlanes
- liveSpecs
- publicationHistory
- storageMapping
- tenant -> billing -> invoices
storageMappings - hasPrevious unexpectedly true
liveSpecs - same behavior with hasNext in another resolver
The following GQL resolvers unexpectedly return
trueforhasPrevious/hasNextpages when given invalid or empty cursors. This is because the pagination logic determines these flag values by the existence of the cursor value, instead of inferring the existence of pages from the returned data.storageMappings -
hasPreviousunexpectedly trueliveSpecs - same behavior with
hasNextin another resolver