Hacker-FEX
diff --git a/‎CHANGELOG.md
Lines changed: 4 additions & 0 deletions b/‎CHANGELOG.md
Lines changed: 4 additions & 0 deletions
diff --git a/‎docs/api.md
Lines changed: 1 addition & 1 deletion b/‎docs/api.md
Lines changed: 1 addition & 1 deletion
diff --git a/‎lib/logger.js
Lines changed: 2 additions & 2 deletions b/‎lib/logger.js
Lines changed: 2 additions & 2 deletions
diff --git a/‎types/log4js.d.ts
Lines changed: 2 additions & 0 deletions b/‎types/log4js.d.ts
Lines changed: 2 additions & 0 deletions
@@ -1,5 +1,9 @@
 # log4js-node changelog
 
+## 4.5.0
+* [Override call stack parsing](https://github.com/log4js-node/log4js-node/pull/914) - thanks [@rommni](https://github.com/rommni)
+* [patternLayout filename depth token](https://github.com/log4js-node/log4js-node/pull/913) - thanks [@rommni](https://github.com/rommni)
+
 ## 4.4.0
 * [Add option to pass appender module in config](https://github.com/log4js-node/log4js-node/pull/833) - thanks [@kaxelson](https://github.com/kaxelson)
 * [Added docs for passing appender module](https://github.com/log4js-node/log4js-node/pull/904)
 
@@ -32,7 +32,7 @@ This function takes a single optional string argument to denote the category to
 * `addContext(<key>,<value>)` - where `<key>` is a string, `<value>` can be anything. This stores a key-value pair that is added to all log events generated by the logger. Uses would be to add ids for tracking a user through your application. Currently only the `logFaces` appenders make use of the context values.
 * `removeContext(<key>)`  - removes a previously defined key-value pair from the context.
 * `clearContext()` - removes all context pairs from the logger.
-* `setParseCallStackFunction(function)` - Allow to override the default way to parse the callstack data for the layout patern, a generic javascript Error object is passed to the function. Must return an object with properties : `functionName` / `fileName` / `lineNumber` / `columnNumber` / `callStack`. Can for exemple be used if all of your log call are made from one "debug" class and you would to "erase" this class from the callstack to only show the function which called your "debug" class.
+* `setParseCallStackFunction(function)` - Allow to override the default way to parse the callstack data for the layout pattern, a generic javascript Error object is passed to the function. Must return an object with properties : `functionName` / `fileName` / `lineNumber` / `columnNumber` / `callStack`. Can for example be used if all of your log call are made from one "debug" class and you would to "erase" this class from the callstack to only show the function which called your "debug" class.
 The `Logger` object has the following property:
 * `level` - where `level` is a log4js level or a string that matches a level (e.g. 'info', 'INFO', etc). This allows overriding the configured level for this logger. Changing this value applies to all loggers of the same category.
 
 
@@ -10,7 +10,7 @@ const categories = require('./categories');
 const configuration = require('./configuration');
 
 const stackReg = /at (?:(.+)\s+\()?(?:(.+?):(\d+)(?::(\d+))?|([^)]+))\)?/;
-function defautParseCallStack(data, skipIdx = 4) {
+function defaultParseCallStack(data, skipIdx = 4) {
   const stacklines = data.stack.split('\n').slice(skipIdx);
   const lineMatch = stackReg.exec(stacklines[0]);
   if (lineMatch && lineMatch.length === 6) {
@@ -44,7 +44,7 @@ class Logger {
     }
     this.category = name;
     this.context = {};
-    this.parseCallStack = defautParseCallStack;
+    this.parseCallStack = defaultParseCallStack;
     debug(`Logger created (${this.category}, ${this.level})`);
   }
 
 
@@ -307,6 +307,8 @@ export class Logger {
 
 	clearContext(): void;
 
+	setParseCallStackFunction(parseFunction: Function): void;
+
 	trace(message: any, ...args: any[]): void;
 
 	debug(message: any, ...args: any[]): void;