Closed DmitryEfimenko closed 9 years ago
+1, having Batarang enabled in my chrome extensions actually breaks our web application in production now.
This is already fixed in v0.7.0, which you should see shourtly.
This is a duplicate of a previous issue. Can you please check existing issues before posting a new on next time? This saves me lots of time. Thanks!
You are referring to issue 179, right?. I understand that it was closed with a resolution of removing hint.js all together.
That's a bit different from what my issue states. I'd love to have hint.js to be a part of batarang. So making it optional would be best. This is more of a feature request.
Sorry if it is indeed a duplicate.
This just removes the console logging. You can still see the messages in the pane. I plan to re-add the options to console log hints, but it's low priority compared to bugfixes.
oh, awesome, thanks!
It appears batarang 0.6 started using angular hint.js, which is quite buggy. hint.js has a great idea, so it's a good thing that more people are now exposed to it. It'll become more stable faster.
However, I think there need to be an option to disable/enable hint.js in the batarang. And while we are at it, perhaps it would also be a good idea to let developer choose which components of hint.js should be enabled.