Closed Sleavely closed 1 year ago
Is there an update on this?
Needs review/merge by @jeremydaly
Hey @Sleavely, thanks for your contribution, this issue was already resolved in a different PR that I've merged, in addition we allow several params and not only two so this code is not correct.
Again, thanks and sorry for the delayed response 🙏
No worries, I'm just glad the issue is being looked at :)
in addition we allow several params and not only two so this code is not correct.
From what I understand, the base logger supports a dynamic amount of arguments while the actual implementation in the Request
object explicitly only accepts two?
Hey @Sleavely, I've dug into this a bit further and you're correct, I misunderstood that part in the code, good catch.
I'll be opening a new PR that adds a test case for this and also fix a typo I've found in the doc. Will add you as a co-author, I hope that's okay with you, I want to release a new version today :)
Thank you very much!
I converted a route to Typescript and things went 💥
Turns out the type definition for the logger methods only expects a string.
This PR makes it behave in accordance with the README