Frontend Tech Community has agreed to create, use, and standardize the @AsyncInlineError() decorator. It will improve our code readability.
This decorator catch-all method errors and each method instead of return a value, will return a tuple like [error, response]. So, with this decorator a method using it will never fail.
On this PR, we provide:
A new @AsyncInlineError() decorator
Update the needed documentation
New linting rules created to push our ADR decisions.
MUST The @AsyncInlineError() must be the first decorator in a method. It will make our life easier when we develop other decorators. The rule provide a quick fix.
SHOULD The @AsyncInlineError() should be used in all UseCase.execute, Service.execute and Repository.method. The rule will NOT provide a quick fix to avoid uncontrolled errors.
@AsyncInlineError()
function execute() {
if(error) {
throw new Error('this is not ok')
}
return 'this is ok'
}
const response = execute()
const [error, result] = response
Description
Frontend Tech Community has agreed to create, use, and standardize the
@AsyncInlineError()decorator. It will improve our code readability.This decorator catch-all method errors and each method instead of return a value, will return a tuple like
[error, response]. So, with this decorator a method using it will never fail.On this PR, we provide:
@AsyncInlineError()decorator@AsyncInlineError()must be the first decorator in a method. It will make our life easier when we develop other decorators. The rule provide a quick fix.@AsyncInlineError()should be used in all UseCase.execute, Service.execute and Repository.method. The rule will NOT provide a quick fix to avoid uncontrolled errors.Related Issue
Example
Client test ✅
Server test ✅