-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add FAQ about browser verbosity levels to prevent questions about debug method not working #172
Comments
Make sure you are not filtering them with the browser.
…On Oct 18, 2017 11:26, "Sergey Bahchissaraitsev" ***@***.***> wrote:
Every other method: error, warn, info, log work fine and print the value,
but debug prints nothing and no error message to be found.
Using chrome Version 59.0.3071.115 (Official Build) (64-bit)
I use in app.module:
import { Logger, Options as LoggerOptions, Level as LoggerLevel } from "angular2-logger/core";
@NgModule({
providers: [
{ provide: LoggerOptions, useValue: { level: 5 } },
Logger
]
})
export class AppModule { }
In the service:
import { Logger } from "angular2-logger/core";
@Injectable()
export class MyService {
constructor(private logger: Logger) {
this.logger.debug("Debug message...")
}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#172>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AKHLTUbGjqvZrqgemrwDaSJw9e5HiH5uks5stiaxgaJpZM4P9_Wf>
.
|
No filter @langley-agm |
Please double check, this has been reported/resolved several times, do a
search in the issues or look for a dropdown in the chrome console filtering
out verbosity msgs
…On Oct 18, 2017 12:39, "Sergey Bahchissaraitsev" ***@***.***> wrote:
No filter @langley-agm <https://github.com/langley-agm>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#172 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKHLTajDC3R2e7UkZ8_MARGpkEOh7WNkks5stje8gaJpZM4P9_Wf>
.
|
@langley-agm looks like you were right. Did notice the drop-down. Thanks. |
I've been meaning to add it to a frequently asked questions in the front
page but I haven't got time, a PR would be welcome :)
On Oct 18, 2017 12:44, "Sergey Bahchissaraitsev" <[email protected]> wrote:
@langley-agm <https://github.com/langley-agm> looks like you were right.
Did notice the drop-down.
How about changing this to add this to the readme so others would have an
easier time finding the source of this issue?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#172 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKHLTXYizYFMXFbysKPxK74RHflxMdH3ks5stjkBgaJpZM4P9_Wf>
.
|
Saw it coming @langley-agm |
bahchis
changed the title
Debug method not working in Chrome
Add FAQ about browser verbosity levels to prevent questions about debug method not working
Oct 18, 2017
This was referenced Nov 2, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Every other methods:
error, warn, info, log
work fine and print the value, butdebug
prints nothing and no error message to be found.Using chrome
Version 59.0.3071.115 (Official Build) (64-bit)
I use in app.module:
In the service:
The text was updated successfully, but these errors were encountered: