Hi Balachandar, Some times ago, there was a few changes to the angular display system. The main change code wise was to remove the compiledScope from the global app variables. You can find the breaking change in this PRs [1] While there we try to make it backward compatible to some degree afterwards [2], it didn't bring all of the options people were using (myself included).
Right now, accessing it the way you did it (targeting the id of a declared element) is probably the best way of doing it. There was also some work done to create some Angular Display front-end functions in case this would come in handy to you [3] [1] https://github.com/apache/incubator-zeppelin/pull/588 [2] https://github.com/apache/incubator-zeppelin/pull/720 [3] https://zeppelin.apache.org/docs/0.6.0-incubating-SNAPSHOT/displaysystem/front-end-angular.html On Wed, Jun 1, 2016 at 5:32 AM, Balachandar R.A. <balachandar...@gmail.com> wrote: > Hello, > > > I used to work with the binary version of zeppelin for our use cases. > While sharing variables of scala interpreter with angular, I use the below > code > > var controllerElement = document.querySelector('[ng-app=zeppelinWebApp]'); > > var scope = angular.element(controllerElement).scope().compiledScope; > > > > > > Yesterday, I pulled the latest code and built. I ran my use case and it > failed in the above lines. After few minutes of digging, I use the below > code, and it worked. > > > var scope = angular.element($("#reset")).scope().compiledScope; > > > Unfortunately, i could not find any information about this behavior. Also, > the "reset" is a div id I have declared in the beginning of my angular > paragraph. This line of code will not work if I do not have any div defined. > > > Can someone please explain this behaviour? > > > > with regards > > Bala >
