Comments (6)
The custom_fields field is meant to be a flat object of key-value pairs and not an array. We decided to write all values as string in order to avoid problems with varying types.
from cf-nodejs-logging-support.
Makes sense. Maybe the example is not clear enough. If I have an object having a field of array type and I log it and want to use it again, the field is no longer an array - it is a string. Isn't there a way to not have this behavior, maybe deep cloning or some sort?
from cf-nodejs-logging-support.
Am I correct, if I asssume you have no Problem with writing your Object as string in your log and want to preserve the object you are logging without any side effects from our library?
We will fix this issue asap.
from cf-nodejs-logging-support.
Thanks. You are correct.
For now we'll stick with 1.1.2 version.
We do want to upgrade because the performance is better with newer versions like 3.0.4.
from cf-nodejs-logging-support.
We fixed this issue in version 3.0.6
from cf-nodejs-logging-support.
👍
from cf-nodejs-logging-support.
Related Issues (20)
- Array with stacktrace is stringified and resulting JSON is incorrect HOT 3
- Removing unnecessary logs HOT 3
- Avoid publishing dev folders like docs & tools HOT 5
- Mend reports for jsonwebtoken-8.5.1 please consider upgrade jsonwebtoken to ^9.0.0 HOT 1
- Possible vulnerability due to missing JWT public key type check
- logMessage is not using the customFields in v7 HOT 2
- CorrelationId not set when creating Child Logger HOT 4
- Fastify support HOT 15
- Winston Support in v7 HOT 3
- Custom fields always converted to strings, even if not necessary.
- custom fields are not logged correctly for request logger HOT 1
- cf-nodejs-logging-support and @sap/logging HOT 4
- using req. context logger in qunit test with nock
- tenant_id still missing in the request logger HOT 3
- ReferenceError: defaultConfig is not defined HOT 1
- Switch off the INFO log on KIBANA HOT 1
- Switch logLevel HOT 3
- Clear (my) confusion: cf-nodejs-logging-support vs @sap/logging HOT 7
- Logs contain incorrect url in "request" field HOT 2
- Extraction of logging level fails with window object HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cf-nodejs-logging-support.