You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were using winston-mongodb 5.1.1 to store our logs.
Trying to upgrade our logger app to winston-mongodb 6.0.0 has broken our reader log app.
Using winston-mongodb 6.0.0, metadata type changed from Array to Object
Our reader log app is currently searching for metadata[index] but as it changes to object, we have to change our reader app but also to handle both type (Array and also Object) for a period.
Is there any way to still save an Array rather than an Object using winston-mongodb 6.0.0 ?
What version of Winston presents the issue?
winston-mongodb v6.0.0
What version of Node are you using?
v20.8.0
If this worked in a previous version of Winston, which was it?
winston-mongodb v5.1.1
Minimum Working Example
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Breaking changes are allowed with major version bumps :) That being said, if this is a big usability issue for you, feel free to open a PR that would support either an array or object mode for the metadata?
🔎 Search Terms
Metadata type change
The problem
We were using winston-mongodb 5.1.1 to store our logs.
Trying to upgrade our logger app to winston-mongodb 6.0.0 has broken our reader log app.
Using winston-mongodb 6.0.0, metadata type changed from Array to Object
Our reader log app is currently searching for metadata[index] but as it changes to object, we have to change our reader app but also to handle both type (Array and also Object) for a period.
Is there any way to still save an Array rather than an Object using winston-mongodb 6.0.0 ?
What version of Winston presents the issue?
winston-mongodb v6.0.0
What version of Node are you using?
v20.8.0
If this worked in a previous version of Winston, which was it?
winston-mongodb v5.1.1
Minimum Working Example
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: