Export multiple arguments of an error as an object to reduce import statements.

[anshgoyalevil]

Is your feature request related to a problem? Please describe.
This issue is related to the refactoring of code, where the multiple arguments of an error are being exported as separate constants. For example:

export const COMMENT_NOT_FOUND = "Comment not found";
export const COMMENT_NOT_FOUND_CODE = "comment.notFound";
export const COMMENT_NOT_FOUND_MESSAGE = "comment.notFound";
export const COMMENT_NOT_FOUND_PARAM = "comment";

this can be converted to an object like

export const COMMENT_NOT_FOUND_ERROR = {
  DESC: "Comment not found",
  CODE: "comment.notFound",
  MESSAGE: "comment.notFound",
  PARAM: "comment",
};

which can further be imported in the codebase as an object, and can replace the error constants such as

if (!comment) {
    throw new errors.NotFoundError(
      IN_PRODUCTION !== true
        ? COMMENT_NOT_FOUND
        : requestContext.translate(COMMENT_NOT_FOUND_MESSAGE),
      COMMENT_NOT_FOUND_CODE,
      COMMENT_NOT_FOUND_PARAM
    );
  }

with

if (!comment) {
    throw new errors.NotFoundError(
      IN_PRODUCTION !== true
        ? COMMENT_NOT_FOUND
        : requestContext.translate(COMMENT_NOT_FOUND_ERROR.MESSAGE),
      COMMENT_NOT_FOUND_ERROR.CODE,
      COMMENT_NOT_FOUND_ERROR.PARAM
    );
  }

Approach to be followed (optional)
The following approach can be followed:

• Create the error objects.
• Search the codebase for the usage of those constants, and replace them with those objects.

Additional context
This will reduce the complexity of codebase import statements, since there are a lot of import statements inside a code file, for the constant, which can be grouped together.

[anshgoyalevil]

@noman2002 @palisadoes Please take a look at this issue.

[KrutikaBhatt]

In case it's fine, can I work on this issue?

[anshgoyalevil]

In case it's fine, can I work on this issue?

Let's wait for others view on this. After that, we can create child issues for it, and work upon them.

[anshgoyalevil]

@xoldyckk What's your view on this?

[xoldd]

@anshgoyalevil It's a good idea.

[github-actions]

This issue did not get any activity in the past 14 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[anshgoyalevil]

@palisadoes
I have unassigned myself from this issue.
This is a good first issue, so want new contributors to get into it. It would give them a thorough understanding of the project.

[KrutikaBhatt]

Can I work on this?

[xoldd]

@KrutikaBhatt assigned you