feat: added support to include service

README.md

@@ -37,13 +37,11 @@ const logger = createLogger({ logLevel: "info" });
 logger.info("Hello world!");
 ```
 
-Additionally, one can create child loggers inherited from the parent/package-default to pass specific metadata. 
-One such use case would be to add `service` metadata while importing it within the context of a service. For example:
+Additionally, one can pass `service` metadata while importing it within the context of a service. For example:
 ```js
 const { createLogger } = require("logger-safe-security");
-const logger = createLogger();
-const serviceLogger = logger.child({ service: "sample" });
-serviceLogger.info("This log line will include service metadata");
+const logger = createLogger({ service: "sample" });
+logger.info("This log line will include service metadata");
 ```
 
 ## Definition

package.json

@@ -1,6 +1,6 @@
 {
   "name": "logger-safe-security",
-  "version": "1.1.2",
+  "version": "1.1.3",
   "description": "Custom logging framework used in SAFE",
   "main": "lib/index.js",
   "types": "lib",

src/index.ts

@@ -6,11 +6,15 @@ export const levels = winston.config.npm.levels;
 
 export type Logger = winston.Logger;
 
-export const createLogger = ({
-    logLevel = "info"
-}: {
-    logLevel: string;
-} = { logLevel: "info" }): winston.Logger =>
+export const createLogger = (
+    {
+        logLevel = "info",
+        service
+    }: {
+        logLevel?: string;
+        service?: string;
+    } = { logLevel: "info" }
+): winston.Logger =>
     winston.createLogger({
         // default log level is "info"
         level: logLevel,
@@ -42,5 +46,5 @@ export const createLogger = ({
         ],
 
         // generic metadata applied to all logs
-        defaultMeta: { type: "application" }
+        defaultMeta: { type: "application", ...(service && { service }) }
     });