Design questions node-express-server

Description

This is not a bug report but more of a question about some design decision of the generated code

1. The service class need to now about http result codes. I don't think a service should now anything about how it is used later. So it should only return data and perhaps throw an exception but it don't know if it is called from a rest-api controller, a cli or another service. But in the template the service functions should return data and http return codes

2. Inside a service function do you create a promise

static someFunction({ someParameter }) {
    return new Promise(
      async (resolve) => {
        try {
          resolve(Service.successResponse(''));
        } catch (e) {
          resolve(Service.rejectResponse(
            e.message || 'Invalid input',
            e.status || 405,
          ));
        }
      },
    );
  }

why not the much simpler declaring the function as async?

static async someFunction({ someParameter }) {
  try {
    return Service.successResponse('');
  } catch (e) {
    return Service.rejectResponse(
       e.message || 'Invalid input',
       e.status || 405,
    );
  }
}

or am I missing something obvious?

openapi-generator version

4.2 (but 5.0 branch is similar)

The issue names the node-express-server generator and its service functions; begin by reviewing the generated templates in the referenced 4.2 and 5.0 branches. Determine whether the service/controller boundary and async error-handling approach should change, then document a maintainer-approved decision before identifying the affected templates and tests.