DynaModel

Generate typed methods for DynamoDB models. With special sauce for nested props.

---

---

Updating Nested Properties

DynaModel utility functions are instantiated with your DB connection, table and its items type, e.g.

import { dynaModel } from '@os-gurus/dynamodel'

const ddb = new DynamoDB.DocumentClient({ region: 'us-east-1' })

type HashKeys = { id: string }
type Props = { address: { country: string } }

const { makeUpdateProperty } = dynaModel<HashKeys, Props>(ddb, 'user-meta')

function updateUserCountry (id: string, country: string) {
  const update = makeUpdateProperty('address.country')
  // property paths are typed and autocomplete ☝️
  return update({ id }, country)
  // returns updated value ☝️ typed as `string`, arguments are also typed
}

When making updates to nested properties, first it will attempt to set the value at the given path, but if the parent doesn't exist it will go recursively upward to create the parent object.

This approach will amortize the cost of requests, as only the first update will result in multiple requests, subsequent updates will just set the nested property and return.

In the instance of setting address.country where no address exists on the item, it would update address to { country: 'AU' }. The next request would just set address.country to AU.

Examples

import { dynaModel } from '@os-gurus/dynamodel'

const ddb = new DynamoDB.DocumentClient({ region: 'us-east-1' })
const table = `service-user-data-${process.env.STAGE}`

type UserKeys = {
  userId: string
}
type UserData = {
  name: string
  address: {
    country: string
  }
}

const usersDB = dynaModel<UserKeys, UserData>(ddb, table)

export const userModel = {
  getUser: usersDB.makeGet(),
  getUserName: usersDB.makeGetProperty('name'),
  updateUserName: usersDB.makeUpdateProperty('name'),
  updateUserCountry: usersDB.makeUpdateProperty('address.country'),
  setDefaultCountry: usersDB.makeInsertProperty('address.country')
}

Known Issues

There's a problem with generating the argument type for property paths from a given object type. It ends up creating quite large definition files that are slow to load and deliver type hinting in the IDE. I know there's better solutions out there in some TS utility packages, just need to find the right approach for this usage. For now I've reduced the depth of the Paths utility type to make the definition files manageable.

---

That's all the docs I've got time for right now sorry. Try it out. The types are nice.