fix: Bind log functions to sanitized context #27

[SwapnilBhosale]

Closes #27

Fix for issue 27 support for log, info,error, warn and verbose methods of context objects

1. Do not add explicit handling for log function in sanitizeContext method
2. remove log related test cases
3. Tested on Azure function and now able to log with all the levels specified

Following are the screenshot :

[codecov-io]

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #29   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           4      4           
  Lines          67     67           
  Branches       18     18           
=====================================
  Hits           67     67

Impacted Files	Coverage Δ
src/IncomingMessage.js	100% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2bd9041...76a8b64. Read the comment docs.

[yvele]

Please don't change the space formatting everywhere..
This also makes the PR very hard to review

Only make changes on what's needed

[SwapnilBhosale]

Please don't change the space formatting everywhere..
This also makes the PR very hard to review

Only make changes on what's needed

• Corrected formatting as it was before.
• Change the stuff which was only needed

[yvele]

So basically the log function can be passed destructured, and don't need to be bound using bind 🤔

Is this compatible will all Azure Function runtimes? What Azure Function version are you using?

I'm also thinking.. in a further commit, to pass contextas it without sanitizing it

[SwapnilBhosale]

So basically the log function can be passed destructured, and don't need to be bound using bind 🤔

Is this compatible will all Azure Function runtimes? What Azure Function version are you using?

I'm also thinking.. in a further commit, to pass contextas it without sanitizing it

I think, Yes, you do not have to bind the log function.
Please check the screenshot atatched for issue #27 .
I have tested on azure function v~1.
Will update you for v2 in some time

[SwapnilBhosale]

So basically the log function can be passed destructured, and don't need to be bound using bind 🤔
Is this compatible will all Azure Function runtimes? What Azure Function version are you using?
I'm also thinking.. in a further commit, to pass contextas it without sanitizing it

I think, Yes, you do not have to bind the log function.
Please check the screenshot atatched for issue #27 .
I have tested on azure function v~1.
Will update you for v2 in some time

Tested on V2. It is also working as expected. Seems, nothing is broken with the fix

[SwapnilBhosale]

Dear Yvele,

We are using this library in production, and we are blocked because of this issue(without context.log.error support we can not monitor azure function for any errors or downtime as in appinsight we look for errors).

Highly appreciate if you can release a minor version asap.

[SwapnilBhosale]

Incorporated formatting changes

[xXanth0s]

So what is the status here?
Is the repository dead?