-
-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Missing requestFields
in DILoggerOptions
#2592
Comments
Romakita
added a commit
that referenced
this issue
Feb 17, 2024
…gger options from PlatformLogMiddleware Closes: #2592
Romakita
added a commit
that referenced
this issue
Feb 17, 2024
…gger options from PlatformLogMiddleware Closes: #2592
Romakita
added a commit
that referenced
this issue
Feb 17, 2024
…gger options from PlatformLogMiddleware Closes: #2592
Romakita
added a commit
that referenced
this issue
Feb 17, 2024
…gger options from PlatformLogMiddleware Closes: #2592
🎉 This issue has been resolved in version 7.61.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Romakita
added a commit
that referenced
this issue
Mar 2, 2024
…gger options from PlatformLogMiddleware Closes: #2592
Romakita
added a commit
that referenced
this issue
Mar 3, 2024
…gger options from PlatformLogMiddleware Closes: #2592
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I tried to use
requestFields
as part of thelogger
object within the Configuration object passed via@Configuration
decorator. As described here: https://tsed.io/docs/logger.html#configurationWell, it's working but only with
// @ts-ignore
because the field is not defined in theDILoggerOptions
.To Reproduce
Just try to use something like
Expected behavior
Typesafe compilation.
Code snippets
No response
Repository URL example
No response
OS
Windows 10
Node version
v18.7.1
Library version
v7.61.0
Additional context
No response
The text was updated successfully, but these errors were encountered: