How to design debuggable errors when working with tryCatch blocks?

[volkanunsal]

Hi all. I'm wondering how you design error messages that make it easier to debug a piped async computation, especially when the error could be coming from several functions. For example, I have the following function:

export function removeFileByName(name: string) {
  return pipe(
    findRecordWithName(name),
    taskEither.chain((record) => {
      return pipe(
        getDocsTable(),
        taskEither.chain(ensurePermissionToDelete(record)),
        taskEither.chain(deleteRecordFromTable(record)),
        taskEither.chain(syncMapFiles),
      );
    }),
  );
}

In this example, the computation may return a Left from either deleteRecordFromTable or ensurePermissionToDelete. When I see an error message from here, I can search for it in the codebase, and if it's one of my own error messages, it's not a problem, but sometimes an error comes from a tryCatch block and that can be frustrating to debug.

I'm looking for any kind of general advice on best practices for writing error messages within chained computations so that it becomes easier to debug them.