FQL Page objects can be arguments to Array functions
FQL Page objects have additional fields like before, and data, that may make it seem like you need to Select to get at the underlying array of results. However, FQL supports passing Page objects directly to functions that operate on arrays and the function will transparently operate on the contained data field.
Paginate(Match(Index("all_customers")))
Drop(1, Paginate(Match(Index("all_customers"))))
Take(1, Paginate(Match(Index("all_customers"))))
Instructor: [00:00] We match for all of the documents in the all customers index. We can paginate on that match just in case there are too many objects to return at any given time.
[00:09] Note that paginate returns a page object, not the array of results itself. However, even though paginate returns a page object, we can still use functions that operate on arrays directly on the page object, as the array functions will pass through the page object to operate on the containing array.
[00:27] For example, we can use drop. If we drop one from the results of our paginate, note that we have two items left in our results, and one item got pushed to the before array in the page result. If we run our paginate query again, a full results set is returned. We have not modified the database with this query.
[00:45] We can also use other array functions, such as take.
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!