[Bug]: SPLAT Format behavior is inconsistent (master issue)

[maverick1872]

Purpose

There appears to be a larger issue within Winston in how the SPLAT format behaves, as well as some side-effects due to hot path optimizations of the log logic. This story is meant to consolidate and track Issues/PRs here in Winston, as well as in WinstonJS/Logform & WinstonJS/Winston-Transport.

Thoughts

Will be fleshed out once I'm confident I have consolidated the majority of issues/PRs regarding SPLAT behavior.

Consolidations

Below is a compiled list of all issues and pull requests I have been able to find regarding this issue. They are sorted newest to oldest. All issues below are going to be marked as a duplicate and then closed. This is being done to hopefully centralize all efforts for resolving this issue to this issue moving forward.

Issues:

• ALWAYS send the ORIGINAL, unmutated info object to each registered logger transport #1933
• Meta properties omitted if message matches splat regex #1709
• multiple transports loosing SPLAT/meta #1430
• Proposed handling of info[SPLAT] #1408
• Meta data doesn't get passed to info object after the update #1381

Pull Requests:

• Don't change behavior when message matches splat regex. #1710
• Info.meta improvements logform#82

Notes

If you're aware of any other Issues or PRs (including those that have been closed) that are not included above please let me know and I'll get them added to the list.

Reproducible examples of issues currently present

When splat format is not configured metadata is not included when a token is found in log message
Metadata not sent to every transport

🔎 Search Terms

splat format

[gcb]

would issues where winston handles multiple args differently than console.log(a, b, c) also fall in this category, or is this only for actual splat formatter? As a user i kinda of clump them all in the same space...