Element-web: Please add config option to disable console.log

Created on 17 Jul 2019  路  4Comments  路  Source: vector-im/element-web

Please add config option to disable console.log.

suggestion

Most helpful comment

Hello,

I agree with @menturion about forced ultra-verbose logs. It's annoying, and also useless if we're not debugging.
And even if we're debugging, we may need our own logs and not those of the "system".
It would be great if there was an option to mute them without touching the rageshake files.
And in production, I personally prefer crystal clean console with zero outputs. It's more "professional".

All 4 comments

Can you explain in more detail what the use case for this is?

Thanks for your reply.

You should have asked your question the other way round: "Could you please explain in more detail what the use case is for prompting that much information in the console".
The only suitable answer I know is "for debug purposes". Please name a single major app that discloses this kind of information: Gmail, Facebook, Instagram, WhatsApp Web, Github, LinkedIn etc...? ... NO.

So please add an option (e.g. "mode": ["production"|"debug"]) to hide all these information in production mode.

Well, we regularly make use of it for debug purposes as it exists today.

So again, what is the reason? Does it just bother you? Do you believe it affects performance? ...something else?

Hello,

I agree with @menturion about forced ultra-verbose logs. It's annoying, and also useless if we're not debugging.
And even if we're debugging, we may need our own logs and not those of the "system".
It would be great if there was an option to mute them without touching the rageshake files.
And in production, I personally prefer crystal clean console with zero outputs. It's more "professional".

Was this page helpful?
0 / 5 - 0 ratings