To help you get started, we've collected the most common ways that resolve-query is being used within popular public projects.

reimagined / resolve / tests / read-models-transactional / worker.js View on Github

break
      default:
        throw new Error(
          `Incorrect process.env.ADAPTER = ${process.env.ADAPTER}`
        )
    }

    const storage = createStorage({
      pathToFile: path.join(__dirname, 'event-storage.db')
    })

    const eventStore = createEventStore({ storage })
    const connectorName = 'default-adapter'
    const readModelName = 'default-read-model'

    const query = createQuery({
      eventStore,
      viewModels: [],
      readModelConnectors: {
        [connectorName]: adapter
      },
      readModels: [
        {
          name: readModelName,
          connectorName,
          projection,
          resolvers
        }
      ]
    })

    await query.read({

View more ways to use resolve-query

resolve-query

Provides an interface for creating and querying Read- and View-Models.

A Read Model is an application state built from the Event Log by Projection Functions and used to reply to Queries. It can be saved into a server-side Storage using an appropriate Read Model Adapter. Queries to a Read Model are processed by Resolver Functions, which can filter, aggregate and/or paginate data before sending it to the client side. You can manage the Resolver behavior using client-defined arguments. In this case, the server-side changes trigger the client-side updates.

A View Model is built on the client side and used to keep the UI up to the current application state. It is built and updated by Reducers. Aggregates whose events should participate in the View Model construction are defined by the aggregateId (in most cases, one aggregate corresponds to one view model, although, a wildcard aggregateId is possible).

import createQuery from 'resolve-query'

const query = createQuery({
  readModelConnectors,
  readModels,
  viewModels,
  eventStore
})

Usage

• snapshotAdapter - An adapter for loading and saving the intermediate Aggregate state. The argument is optional, snapshots are not used by default.
• readModelConnectors - A Read Model connector instances.

Read models

Pass the following arguments to the factory function to create a Read Model:

• projection - An object with Projection Functions used to handle incoming Events and build the Read Model.
• resolvers - An object with Resolver Functions. Each function should accept two arguments: the first argument is a reference to the target Read Model. The second argument is an object with fields used to extract data from a Read Model Storage.

A Read Model supports the following functions to query data:

• read - Performs a query within a Read Model via Resolvers. The first argument is a Resolver name; the second one contains an object with the Resolver function properties. Returns the Resolver execution result.
• dispose - Removes the Read Model. Invokes the Read Model Adapter's disposal mechanisms and stops listening to the Event Store bus. The default adapters' disposal operation disconnects with the storage and drops stored tables.

View models

Pass the following arguments to the factory function to create a View Model:

• projection - A map of Redux-like Reducer functions. A function per each event type.

You can access Resolvers and query data from Read Models using a Facade, which supports the following functions:

• read - Performs a query from a View Model using Resolvers.
• dispose - Deletes the View Model (for internal use).