Release 6.0 - 230629.5.2

This release includes new functionality to set field level config as well as improvements to cold start times on certain regularly used queries.

Features

Field level config

This new function allows more customisation of Skylark by allowing you to configure how your fields are displayed in the Skylark UI.

For example, you can change the position or type of field displayed on a per field basis. This is set in the setObjectTypeConfiguration mutation which has previously just been used for object level config.

This example sets the position and type of the title and synopsis fields for a Movie.

mutation {
  setObjectTypeConfiguration(
    object_type: Movie
    object_type_config: {
      field_config: [
        {
          ui_position: 1
          ui_field_type: STRING, 
          name: "title"
        },
        {
          ui_position: 2
          ui_field_type: TEXTAREA, 
          name: "synopsis"
        }
      ]
    }
  ) {
    field_config {
      ui_position
      ui_field_type
      name
    }
  }
}

New instances of the Skylark will include config for every field pre-baked into our entertainment data model. You can check the config with the getObjectTypeConfiguration query.

query {
  getObjectTypeConfiguration(object_type: Movie) {
    field_config {
      name
      ui_position
      ui_field_type
    }
  }
}

Cold start improvements

We love our serverless functions at Skylark, it allows us to be dynamic and easily scale. However we've noticed that cold starts can cause a significant drag on certain critial queries and mutations.

We've now added countermeasures for this to the following functionality:

• search
• getObject
• getSet
• createObject
• updateObject
• deleteObject

We will continue to monitor the performance and cold start times, and be making tweaks over the next few weeks.