I'd suggest that we remove the console.log and console.warn output or at least replace it with console.debug (browser-code-reader.ts)
enhancement
werthdavid
👍2
All 4 comments
Are those needed?
I think all of them could be removed from builds, as they are only used in development of the library. If the library works, no one will use them. If someone would like to debug the library they will pull the repo and see the console.
csutorasr
on 26 Feb 2018
👍2
Please, note that I'm publishing under a v0.0.0-**dev**.<hash> tag, I intend to remove these logs at the final version as well. 馃槃
odahcam
on 26 Feb 2018
Done.
odahcam
on 26 Feb 2018
👍1
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
![lock[bot] picture](https://avatars.githubusercontent.com/in/6672?v=4&s=40)
lock[bot]
on 1 Aug 2019
Was this page helpful?
0 / 5 - 0 ratings
Related issues
odahcam
路
6Comments
rohitxsh93
路
9Comments
ramdanegie
路
6Comments
mattiaskagstrom
路
8Comments
jack750155
路
8Comments
Most helpful comment
Are those needed?
I think all of them could be removed from builds, as they are only used in development of the library. If the library works, no one will use them. If someone would like to debug the library they will pull the repo and see the console.