We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
console.warn
console.error
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
Do you want to request a feature or report a bug?
What is the current behavior?
What is the expected behavior?
We should use console.warn to log warnings unless console.error is being used for a good reason.
There is a brief discussion/suggestion to use console.warn to log warnings in this thread: Suggestion: Warn when bindActionCreators encounters non-function property #2279
Incase we decide to go with this, here is the PR with proposed changes: Use console.warn to log warnings instead of console.error #3030
The text was updated successfully, but these errors were encountered:
This is inherited from fbjs's warning, which was previously used. It's explained here: facebook/fbjs#94 (comment)
warning
Sorry, something went wrong.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Do you want to request a feature or report a bug?
What is the current behavior?
console.error
instead ofconsole.warn
to log warningsWhat is the expected behavior?
We should use
console.warn
to log warnings unlessconsole.error
is being used for a good reason.There is a brief discussion/suggestion to use
console.warn
to log warnings in this thread: Suggestion: Warn when bindActionCreators encounters non-function property #2279Incase we decide to go with this, here is the PR with proposed changes: Use console.warn to log warnings instead of console.error #3030
The text was updated successfully, but these errors were encountered: