You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the local storage andlogKey exists, the module logs to the console despite the value in localStorage. This is somewhat documented in that you state you should delete the key if you want to disable logging. That said it is somewhat misleading that setting ANY value for the andlogKey will allow log messages to to be output to the console. If you set the key to false, messages are still output.
The text was updated successfully, but these errors were encountered:
That said, it doesn't mean this module has to work this way. Open to suggestions, we could, for example, change it to check for the existance of the key and also make sure it's not the string false. Or, perhaps it should just be better explained in the readme.
Either solution works for me, just opened the issue because it did trip me up. I was just setting the andlogKey value from clientconfig and was confused why it wasn't working.
It does seem a little cleaner to actually evaluate the key since you suggest setting the key value to true. That said, just documenting it a bit better would be sufficient.
If the local storage andlogKey exists, the module logs to the console despite the value in localStorage. This is somewhat documented in that you state you should delete the key if you want to disable logging. That said it is somewhat misleading that setting ANY value for the andlogKey will allow log messages to to be output to the console. If you set the key to false, messages are still output.
The text was updated successfully, but these errors were encountered: