0.6 is problematic #170
Comments
Can you provide me with some more information? There's not enough for me to go off with just that. |
I also woke up to an issue with 0.6 update. The issue for me seems to be that it changes the bootstrapping-process somehow. Since I have some URLs should be triggered/set directly after "angular.bootstrap", and these values are now set to null instead. |
0.6 also broke my app, I think due to hint.js My ng-show directives were no longer digesting scope property updates on the controller. Disabling Batarang fixed the issue.... |
Same here disabling solves it |
Yeah, I can confirm this. Updated chrome to beta 40 and batarang is 0.6 and my app that was working yesterday didn't start, I disabled batarang and it's working now. |
Okay, I can confirm that it has to do with hint.js from my side. |
It seems Batarang is looking for some controllers in hint.js, not im my source files. |
Uncaught TypeError: undefined is not a function |
It has broken all of our client sites (more than 200 sites) based on angularjs. Check out www store hippo dot com. Please review and revert asap. |
Okay, so this seems to actually be a known issue with angular-hint? It is even reported by btford. So perhaps the temporary solution is to revert back to 0.5, add functionality to disable ng-hint (since this contains the bug). Of course the issue should be handled, but from my point it looks more like a angular-hint issue. |
Same issue here. I get a blank page on load with the plugin enabled. For me, everything seems to render when I refresh. Disabling the plugin also makes the page render on initial load. I don't know how useful it is to provide a reproducible example as it seems to be many people experiencing this. |
previous version 0.5.0 seems to be broken as well. |
0.6 seems to work as advertised on Chrome 39/Linux, however is there a way to disable hint.js temporarily? The hinting seems to be dragging my livereload down to a crawl. |
same here with angular1.2.16, angularjs-batarang 0.6.0, chrome 39.0.2171.95 m/windows. you can check it on http://group.tripcake.at/demo |
Broken oh so broken! Looking through the console I see that 'hint.js' is the problematic in my (1st ?) case:
return function ngEventHandler(scope, element, attrs) {
for(var attr in angularAttrs) {
var boundFuncs = getFunctionNames(attrs[attr]);
boundFuncs.forEach(function(boundFn) {
if(ngEventDirectives[attr] && !(boundFn in scope)) {
messages.push({
scope: scope,
element:element,
attrs: attrs,
boundFunc: boundFn
});
}
});
}
element.on(eventAttrName.substring(2).toLowerCase(), function(event) {
scope.$apply(function() {
fn(scope, {$event:event});
});
});
formatResults(messages);
}; on line var boundFuncs = getFunctionNames(attrs[attr]); I have a form with and when calling // ...
module.exports = function getFunctionNames(str) {
var results = str.replace(/\s+/g, '').split(/[\+\-\/\|\<\>\^=&!%~]/g).map(function(x) {
// ... the Hope that helped. |
I'm having issues as well, using Angular 1.3.2. Here's a stacktrace:
I hope it helps. |
You can roll back to 0.4.3 of Batarang until the issues are resolved. Instructions here: http://stackoverflow.com/a/27404493/633107 |
Failed to instantiate module ngHintModules due to:
RangeError: Maximum call stack size exceeded
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2335:21)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2386:5)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2389:7
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2387:21)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2389:7
at Array.forEach (native)
at module.exports (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2387:21)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:2389:7 Seeing a similar issue here. |
Just posing stack traces and error messages are somewhat helpful, but better would be to post reproductions. |
@mickeyvip – the issue you described was fixed in v0.7.1. |
I'm going to close this issue, since there are other similar reports that include more information, and I've since pushed many fixes. Can you all please:
This will help me stay organized and roll out fixes as fast as possible. Thanks! |
@btford yes, updating to v0.7.1 fixed it. Thank you |
@btford All good. Thank you. |
Our app won't start because of 0.6 update from 12-09-2014
What's going on?
The text was updated successfully, but these errors were encountered: