Access context after run

Some of my tasks perform operations, like connecting to a database, and that db connection is stored on the context.

Regardless of if the pipeline succeeds or fails, whenever it’s all finished, I need to close these connections.

I know that if run succeeds , ctx will be the first argument listr.run((ctx) => { ctx.db.close(); } would work fine. But how do you handle the case where it fails? listr.run().catch((err) => { // how to get ctx here?

Ideally for my case, it would be available on the listr object itself, so I could use it in finally (although, I would also settle for something like listr.run(closeConn).catch(closeConn)

I was expecting this to work, but it looks like listr.options.ctx is undefined

const listr = new Listr([
  {
    task: async (ctx) => {
      ctx.test = 'test';
      throw new Error('force error');
    },
  },
]);

listr.run().finally(() => {
  console.log('options.ctx', listr.options?.ctx);
});

Any ideas?

[cenk1cenk2]

https://listr2.kilic.dev/getting-started/the-concept-of-context#as-class-object

[cenk1cenk2]

The errors collected have a snapshot of the context object, which can be seen here. But it is an array since not-failing errors are also collected.

If we add a similar approach it would be like this, which is not much different than taking the context outside. But I see your point, it does not make much of a sense since it should be an internal variable, I completely agree with that.

const tasks = new Listr({})

try {
  await tasks.run()
} catch {
  // as in the tasks.err
  await tasks.ctx.closeConnection()
}

With the current error structure you can have the last error therefore the context as follows:

const tasks = new Listr({})

try {
  await tasks.run()
} catch {
  // as in the tasks.err
  await tasks.err.pop().context.closeConnection()
}