-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Provide an option to suppress the dev-mode warning message #5556
Comments
Is this really the case? Does react-native require user interaction on console.warn? I could not find anything about that online. EDIT: You are right, it will show a visible yellow box: https://kadikraman.github.io/react-native-v2/debugging You can make a PR for that, but notice that |
👍 I'd use this option even in our web app |
Fixed and released in the latest release. Thanks @jonnyreeves |
Awesome thanks for shepherding my first change to this awesome library.
Just getting my head around firestore replication for my own project but
happy to support further changes in future!
…On Tue, 30 Jan 2024, 17:43 Daniel Meyer, ***@***.***> wrote:
Fixed and released in the latest release. Thanks @jonnyreeves
<https://github.com/jonnyreeves>
—
Reply to this email directly, view it on GitHub
<#5556 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQ36OI6FNPE3XKOVDJ4V3YREWMDAVCNFSM6AAAAABCNSDRPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXGU3DSMBSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Needs a docs update |
@adam-lynch Yes, added here 2bf8467 |
The dev-mode warning written to
console.warn()
triggers a toast in react native development builds which needs to be dismissed each time the app is started.I understand this is a helpful message for some, but once acknowledged it would be a better developer experience if it could be supressed.
I propose this could be achieved through a
process.ENV
check, something like:Happy to raise a PR if others are aligned?
The text was updated successfully, but these errors were encountered: