Hi
I see this issue was discussed in
https://github.com/apache/incubator-zeppelin/pull/720 and looks like for
providing backward compatibility, the compiledScope is made available. I
checked the master version and I see the below lines in
https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-web/src/app/notebook/paragraph/paragraph.controller.js
$scope.paragraph = null;
$scope.originalText = '';
$scope.editor = null;
var paragraphScope = $rootScope.$new(true, $rootScope);
// to keep backward compatibility
$scope.compiledScope = paragraphScope
I thought the commit for backward compatibiity is merged with the master
and it should work if we use master now. No?
regards
Bala
On 21 March 2016 at 19:49, Corneau Damien <cornead...@gmail.com> wrote:
> Hi,
> If you use master, this won't work.
> The scope storage was changed, and it is now kept in the paragraph
> controller only. (Scope can be applied to notebook or specific paragraphs
> from backend)
>
> One way to deal with this would be to have a div with an id in your
> paragraph 2, then access that dom element parent scope (which would be the
> paragraph scope)
> On Mar 21, 2016 5:58 PM, "Balachandar R.A." <balachandar...@gmail.com>
> wrote:
>
>> Hello
>>
>> This is my para 1
>>
>>
>> var name = "bala"
>> z.angularBind("name",name)
>>
>> This is my para2
>>
>> %angular
>> <script type="text/javascript">
>> var controllerElement = document.querySelector('[ng-app]');
>> var scope = angular.element(controllerElement).scope().compiledScope;
>> console.log(scope.name);
>> </script>
>>
>>
>> I ran para 1 and then para 2. Expected to see "bala" as output but this
>> did not print anything. what could be the issue here? I do not see any
>> error log as well in my browser console.
>>
>> regards
>> Bala
>>
>
