30 October, 2024

Validate your config file with the CLI

Running the keel validate CLI command will now, in addition to checking your Keel schema, also validate your keelconfig.yaml configuration file, as demonstrated in the example below.

Enabling and disabling transactions in functions

Mutation function hooks (on create or update actions) and the write custom function are, by default, wrapped in transactions. This means that if an error occurs in your code the transaction will get rolled back and no mutations will persist to your database. All other functions have transactions disabled by default.

This is a great default but there are times where you might want to explicitly enable or disable transactions for your functions. We now support this by exposing a function config from which you can set autoTransaction accordingly.

For example, below we demonstrate enabling transactions for a job.

MyJob.config = {
  autoTransaction: true,
};
 
export default MyJob(async (ctx, inputs) => {
  // ...
});

Simirlarly, we can disable transactions for some write hook.

const hooks: MyFunctionHooks = {
  beforeWrite: async (ctx, inputs, values, record) => {
   // ...
  },
};
 
MyFunction.config = {
  autoTransaction: false,
};
 
export default MyFunction(hooks);

Please make sure to update your CLI by running npm install -g keel.

For any issues or feedback, please visit the support channel on our community Discord (opens in a new tab) or contact us at help@keel.so.

Thank you for using Keel!