I'm attempting to capture errors in nested asynchronous functions to perform a rollback if an error occurs.
Initially, I have a try-catch block where I call a function that then calls another function. The final function should throw an error, and I anticipated that the initial try block would catch this error. However, it does not. Here is my code:
The function with the initial try/catch block:
exports.add = (req, res) => {
const { product, type } = req.body
try {
switch (type) {
case ProductsTypes.TRACK:
addTrack(product, req.files)
res.status(200).json({ message: 'SUCCESS !' })
break
default:
res.status(400).json({ message: 'INVALID TYPE !' })
}
} catch (error) {
// ROLLBACK HERE
res.status(400).json({ message: "Error Exception, Need to rollback", error })
}
}
The function where I expected to catch the error to send it back:
const addTrack = (product, files) => {
const imageFile = files[NamesAddTrackForm.TRACK_IMAGE][0]
const audioFile = files[NamesAddTrackForm.TRACK_AUDIO][0]
const stemsZip = files[NamesAddTrackForm.TRACK_STEMS][0]
FilesFormatter.resizeImage(imageFile, 500, 500) // It was assumed that this function would throw an exception
}
The function where I intentionally throw the error:
resizeImage = (file, width, height) => {
try {
sharp(file.path)
.resize(width, height)
.jpeg({ quality: 90 })
.toBuffer((err, buffer) => {
fs.writeFileSync(file.path, buffe, (err) => { // Here, I purposely introduced an error by misspelling buffer as buffe
if (!err) {
throw Error(err)
}
})
})
} catch (error) {
throw Error(error)
}
}
I am seeking guidance on how to effectively manage these types of errors to relay them back to the primary one. This approach will help me implement similar logic in other files for rolling back actions like database insertions or file creations in case of errors during code execution, preventing illogical data accumulation.