Building fields dynamically results in controller error about trnggrid

[MoonStorm]

Can't replicate the issue on the interactive demo page: http://moonstorm.github.io/trNgGrid/release/index.html#/GlobalOptions

The site is using Angular 1.2.9. Could you upgrade to this version? If that doesn't work, I'm gonna need to see some markup.

[Abrham-Smith]

Will work on upgrading Angular and testing it with 1.2.9 and let you know what happens.

[MoonStorm]

closed due to lack of activity

[trouxmitch]

My timing is terrible. I'm seeing the same thing on Angular 1.2.24. I haven't updated to 1.3 yet to test it there, however. Let me know if I can provide any additional information. I was having problems with the grid automatically picking up changes to a dynamic set of columns, so I started using the "fields" attribute in the

element based on the data returned from the $http call. That appears to work okay, but it's throwing these errors in the console regardless.

Error: [$compile:ctreq] Controller 'trNgGrid', required by directive 'trNgGridBodyCell', can't be found!
http://errors.angularjs.org/1.2.23/$compile/ctreq?p0=trNgGrid&p1=trNgGridBodyCell
    at VALIDITY_STATE_PROPERTY (http://localhost:9000/bower_components/angular/angular.js:78:12)
    at getControllers (http://localhost:9000/bower_components/angular/angular.js:6536:19)
    at nodeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6685:35)
    at compositeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6098:13)
    at nodeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6698:24)
    at compositeLinkFn (http://localhost:9000/bower_components/angular/angular.js:6098:13)
    at publicLinkFn (http://localhost:9000/bower_components/angular/angular.js:5994:30)
    at $get.boundTranscludeFn (http://localhost:9000/bower_components/angular/angular.js:6118:21)
    at controllersBoundTransclude (http://localhost:9000/bower_components/angular/angular.js:6725:18)
    at ngRepeatAction (http://localhost:9000/bower_components/angular/angular.js:20567:15) <td tr-ng-grid-body-cell="0" field-name="comments" ng-style="{'width':columnOptions.cellWidth,'height':columnOptions.cellHeight}" class="ng-scope"> angular.js:10061(anonymous function) angular.js:10061$get angular.js:7357nodeLinkFn angular.js:6687compositeLinkFn angular.js:6098nodeLinkFn angular.js:6698compositeLinkFn angular.js:6098publicLinkFn angular.js:5994$get.boundTranscludeFn angular.js:6118controllersBoundTransclude angular.js:6725ngRepeatAction angular.js:20567$watchCollectionAction angular.js:12385$get.Scope.$digest angular.js:12512$get.Scope.$apply angular.js:12777done angular.js:8371completeRequest angular.js:8585xhr.onreadystatechange

[MoonStorm]

If you could isolate the problem in a simple scenario showing the error and post a jsFiddle that would be of great help.

[trouxmitch]

Sorry for the late reply - I think the GH emails were getting caught by my spam filter. I'll see if I can build something simple and send your way.

[stevek-pro]

First of all trnggrid is great! Thank you for your work and most of all for sharing it!

Now.. I am seeing the same issue when loading data via JSON in the Controller where trnggrid is also controlled from. When loading the data vie resource in my ui router setup I am not seeing the issue. I will try to repo the issue for you in a fiddle or plunkr. I am using Angular 1.2.25 - I need it for ngStrap, albeit this (in my case: avoidable) issue trnggrid runs fine.

[panuhorsmalahti]

I also have this issue. I'm using Angular UI-router.

[youami]

Same here, with Angular 1.3.2

[panuhorsmalahti]

Just an update: the error disappeared when I changed to paging for some reason. (There were other code changes so I'm not 100% sure this was the change).

[Doname]

Hi MoonStorm, here is a jsfiddle: http://jsfiddle.net/4erni/vyedwyvg/ same as in http://jsfiddle.net/howieweiner/fhk93vdr/3/. Diff in bootstrap: 3.3.0, angular: 1.3.1.

[Doname]

Fiddle is updated and running ok. Change in syntax, view fiddle at http://jsfiddle.net/4erni/vyedwyvg/3/

[youami]

@panuhorsmalahti, I switched to pagination but it did not resolve the issue. Can you please pin point other changes you made that might've affected this?