Using the modules's name instead of modules's name.property.#7
Using the modules's name instead of modules's name.property.#7johnkchiu wants to merge 1 commit into
Conversation
|
Thanks @johnkchiu. I think this is going to be safe, albeit not backward compatible so will require a major version change. There's a caveat I remember dealing with, however can't remember the details, but it has to do with naming. Internally, winston capitalizes the exported transport constructors, but internally IIRC the instances are mapped to lowercase names. So uniqueness is, unfortunately, case-insensitive which may cause subtle bugs. Other than ensuring the internal transports can be extended correctly, can you please add tests for issue #6 if this is intended to fix it. (This will be a major rev so I'd like to have tests to back the anticipated behavior.) Thanks again. |
|
I'm not a fan of this change either, but having config for the same transport is useful. Another approach is to add some addition properties to Adding
|
Currently for config such as:
MongoDBis used as the transport name. This shouldn't be the case because:propertyis an optional value so if not provided, it'll be undefined.(This also allows me to use winston-file transport twice for issue #6.)