fix - docs - hooks - error handling

[wallasfmorais]

Checklist

• (n/a) run npm run test and npm run benchmark
• (n/a) tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows Code of conduct

[mcollina]

I would remove the try-catches and rethrow altogether.

[delvedor]

I agree with @mcollina.

[wallasfmorais]

(1):

const result = await asyncMethod()
// Error occurred
if (!result) {
throw new Error('Some errors occurred.')
}

or
(2):

await asyncMethod()
// Error occurred
throw new Error('Some errors occurred.')

[mcollina]

1. or even remove completely the throw.

[wallasfmorais]

Alright, in a moment.

[RafaelGSS]

😕 In "files changed" show me an alteration that I already did it 321c6b6.

I think that is a bug of Github.

[wallasfmorais]

Same here, I saw just before I send the PR.
Even fork from 1 min before and was the same.

Without knowing what to do, I keeped.

[wallasfmorais]

So, I close this and send another PR or no need?

@mcollina, @delvedor

[mcollina]

lgtm

[delvedor]

LGTM

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.