You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the paginated query support implemented in #763, we automatically return a PageInfo object if a user sends a limit in their query. We should change the behavior to return the PageInfo object only if it is requested.
edit: Here's additional info.
During a sync with a member of the frontend team, they gave an example of a query that they would typically use:
As you can see, this query specifically requests for the PageInfo metadata object to be returned. Upon clarification, they said that the front-end team would rather the PageInfo object only be returned if requested instead of how I originally implemented it (the current behavior is to return it for all paginated queries and it's unable to be specifically requested).
The text was updated successfully, but these errors were encountered:
@deekerno This seems simple enough for me to handle if you prefer (also happy to let you have it if you have a certain way you'd like to see it implemented).
As part of the paginated query support implemented in #763, we automatically return a
PageInfo
object if a user sends a limit in their query. We should change the behavior to return thePageInfo
object only if it is requested.edit: Here's additional info.
During a sync with a member of the frontend team, they gave an example of a query that they would typically use:
As you can see, this query specifically requests for the
PageInfo
metadata object to be returned. Upon clarification, they said that the front-end team would rather thePageInfo
object only be returned if requested instead of how I originally implemented it (the current behavior is to return it for all paginated queries and it's unable to be specifically requested).The text was updated successfully, but these errors were encountered: