Closed thulasirajkomminar closed 3 months ago
@bednar Thought about just adding a simple logger but then I wanted to follow the V2 standards :) . So I like this simple implementation so modified my commit.
Should we add log level to ClientConfig
or should we override the defaults like this on the user side
influxdb3.ConfigureLogger(map[string]bool{"debug": false, "info": true, "warn": false, "error": true})
Should we add log level to
ClientConfig
or should we override the defaults like this on the user sideinfluxdb3.ConfigureLogger(map[string]bool{"debug": false, "info": true, "warn": false, "error": true})
Good catch! 👍 You are right it should be a part of ClientConfig.
Should we add log level to
ClientConfig
or should we override the defaults like this on the user sideinfluxdb3.ConfigureLogger(map[string]bool{"debug": false, "info": true, "warn": false, "error": true})
Good catch! 👍 You are right it should be a part of ClientConfig.
@bednar could you verify?
For simplify our codebase we can use default logger:
@bednar Could you have a look?
I think the PR needs to be rebased or main merged into it to use fixed CI and have workflow
check pass.
Code coverage check will probably fail because code coverage will decrease as there is quite a few lines not covered by unit tests (#80), but that could be ignored for now...
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 74.54%. Comparing base (
94c8385
) to head (bad20af
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Closes #73
Proposed Changes
Briefly describe your proposed changes:
Added log package to solve issue https://github.com/InfluxCommunity/influxdb3-go/issues/73
Checklist