How does one actually query db data in KS5?

This is probably a dumb question, but… what’s the API for actually executing a query in KS5? In KS4 there was keystone.list("foo").model.find (mongoose queries). I can’t figure out what functions actually accepts the new GraphQL strings 😬 The TODO demo in this repo doesn’t enlighten me either… and the GraphQL API page in the docs is blank… Do you use keystone.executeQuery?

I can’t figure out the whole business with Apollo either. Is that only necessary with the Next integration, but not static?

[jesstelford]

This is a great question! One we need to do a better job of answering in the docs.

1. keystone.executeQuery is what you’ll use 99% of the time - it accepts a GraphQL query string and does all the heavy lifting for you in terms of optimising queries for the particular database adapter in use and resolving relationships, etc. I highly recommend trying this method first. Except when;
2. You can use the query action which is passed to hooks in the last argument. This is the same as keystone.executeQuery except it executes the query as the currently authenticated user (if your provide the skipAccessControl: true option to the second argument of query, it will behave identically to keystone.executeQuery.
3. To get access directly to the adapter and construct your own queries, there’s no “official” API (really you should be using keystone.executeQuery wherever possible), but the escape hatch for now is the keystone.adapters object which you can play around with to do raw mongoose or SQL queries.

Apollo comes in two halves;

1. A GraphQL server implementation. We use this to power the app-graphql server. The fact that it’s Apollo should be treated as an implementation detail.
2. A client library for making complex cached requests to any GraphQL API. While we use this in the Admin UI, it is 100% not necessary.

In fact, the simplest was to query a GraphQL API is by sending a string in the body of a fetch(). The next simplest way is using the graphql-request npm library which has no caching or any other smarts. Then you get up into the kind-of smart query builders such as urql and draqula, and finally into the really complex caching mechanisms as used by apollo & relay.

[MadeByMike]

BTW if you are after a SPA - the StaticApp is probably what you want. https://v5.keystonejs.com/keystone-alpha/app-static/ Set the fallback route to your SPA index file and all routes will be redirected there.