NodeJS starter setup.

[RobusGauli]

Completed

• Async store integration for request sensitive context propagation.
• RequestID and namespace integration for logs.
• Better transaction management for creating new resource via knex.
• Pagination capability.
• Removed error codes from Custom errors.
• Return requestID for during response error.
• Refactor on promise based statments block.

Need to be done:

• Docker compose for mysql instead of postgresql.
• Common utils (for object manipulation).

[kabirbaidhya]

You can keep this. Instead, add your name too in a separate contributors list.

[kabirbaidhya]

Why different results in between cases? I think it could only be - token or null OR token or error.

[mesaugat]

Yep.

[RobusGauli]

Generally, user of the API when we tend to return null, undefined, "" or throws have the tendency to check for the error like so:

if (!token){}

OR

 if (token === ""){}

OR

try{ // statements }catch(err){}

all of which are optional if user choose not to handle the error properly.

Agreed that return signature and method is a bit verbose here, however i think it forces dev to handle error explicitly. Allows dev to treat error as just another value.

Any thoughts? This is not the typical JS standard way of error handling however languages like go, rust follows the Tuple/Enum pattern.

[mesaugat]

Some go-langish stuff here.

[kabirbaidhya]

Make it straight. Either return null to signify empty value or throw an error to state the failure -- nothing in between.

[mesaugat]

Make it consistent with other LOG_ env variables.

process.env.LOG_ENABLE_FILE_TRANSPORT

[RobusGauli]

@mesaugat, its acts as a flag, may be maintain consistency over semantics? I think ENABLE_FILE_LOG_TRANSPORT is easier to reason?

[mesaugat]

I'd choose consistency because in the long run these variables will grow and it will be a mess.

It's for you to decide.

[mesaugat]

A bharyang would look nice.

import userRoutes from './route/user';
import authenticateUser from './auth';
import swaggerSpec from './utils/swagger';

[kabirbaidhya]

Couldn't be more simple than this.

Suggested change

	const { ok, token } = extractTokenFromHeaders(req.headers);
	if (!ok) {
	const token = extractTokenFromHeaders(req.headers);
	if (!token) {