Closed rhaag71 closed 9 years ago
Assigning @erwinmombay to this, he's tackled this area of the code before. Thanks for the report
will look into this
this should be fixed when we do a new release.
/cc @btford
actually, @rhaag71 would you mind letting me know what batarang version you are using? as I can't seem to to replicate it blowing up on master with your scenario (granted batarang isnt working either, so it probably just got suppressed)
@rhaag71 nevermind, got it to blow up (i had the fix in my local, my bad). but yes a new release should prevent batarang from blowing up the users app when parsing error occurs. my apologies
Awesome, no worries either.. glad you guys had a fix for it. BTW, when will the fixed version release?
It's all rolled up, just needs to go out. Not sure where in the system the breakdown occurred.
Update's out! (It make take up to an hour for it to propagate everywhere). Please reopen if this isn't fixed.
yep should be fixed. let us know if it still blows up! appreciate the detailed report!
In receiving errors like this (see bottom of post), and after much "Undo action" and banging head against wall, I realized that I "enabled" the batarang extension right before receiving the errors (there are actually two occurances of this error, both involving ng-repeat if that helps). When I turn of (or just uncheck "enable") the error goes away. Seems evident that somehow the extension is causing the error, but I'm not exactly sure how/why... (yet).
Also, before I realized that I suspect the extension, I was able to make the error go aways by removing (in the case of the error posted below) this code from my Jade template:
It will be reproducible on my machine and I can provide more info if you like.
This error throws 51 times, same amount of times in the ng-repeat that is getting hit by the error.