Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/720#issuecomment-186354190
I think accessing compiledScope is more like a hack, because of it wasn't
an officially exposed api for notebook users, in the end, providing some api
for javascript, such as `z.scope()` to get current scope object and documenting
it is better way to go.
We used to have compiledScope in Notebook level, and App level. This PR
brings one of compileScope. So some notebook might fixed, some notebook might
still have problem.
I'd suggest, we merge it as a effort for minimizing internal API change.
Whatever user use, we need to minimize Zeppelin breaks notebook working
version by version.
And this PR definitely reduce notebook breaking.
Once we develop officially supported API, such as `z.scope()` then,
reference to compiledScope can be deprecated and removed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
