incubator.apache.org<mailto:users@zeppelin.incubator.apache.org>"
mailto:users@zeppelin.incubator.apache.org>>
Subject: Re: Problem with angular scope
There has been some changes and refactoring of the angular display system,
however I don't think we really loose anything in term of
There has been some changes and refactoring of the angular display system,
however I don't think we really loose anything in term of functionality.
Currently its breaking a few notebooks accessing the scope with javascript.
Since there was no official/proper way to access the scope variables using
Hi Damien
I am not so familiar with the terms you mentioned (app vs paragraph),
so does that mean that we loose in term of functionality from 0.5.6 and dev?
What is the plan to share variables between spark and angular ?
Thanks
Guillaume
On Tue, 22 Mar 2016 at 06:51 Corneau Damien wrote:
> Yes
Yes, it was merged, you can see the discussion in that PR.
The compatibility was only restored for paragraph so that it allow this
method to work:
https://gist.github.com/granturing/a09aed4a302a7367be92
Access from app level wasn't restored
On Tue, Mar 22, 2016 at 2:40 PM, Balachandar R.A.
wrote
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/ze
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 e
