[Bug][Jupyter Widget] The Config panel with the {} menu item to copy&paste the config doesn't work in 0.3

[ramayer-fli]

Describe the bug

The "config-panel" described in the documentation here:

https://docs.kepler.gl/docs/keplergl-jupyter#config-panel

that used to appear with kepler.gl 0.2.2 does not appear with kepler.gl 0.3.0

To Reproduce

Steps to reproduce the behavior:

In a Databricks notebook:

%pip install keplergl

import keplergl
map = keplergl.KeplerGl(height=600)
map.save_to_html(file_name='/tmp/keplergl_test.html')
# now copy that HTML file  and view it in a browser.

Expected behavior

Quoting the documentation "Config can be copied from the side panel with the {} icon."

Exactly as it works if you %pip install -q keplergl==0.2.2

Screenshots

[I can come back and edit this later with screenshots]

Environment (please complete the following information):

• Python version: python3
• keplergl Widget version 0.3.0

Additional context

While it's not too important in Jupyter Lab (where there are other ways of getting the config), in Databricks Notebooks, that {} widget was the only way I can find for extracting the config.

[dscarlat]

Hi, any way to get config in Databricks Notebooks while this issue is solved?

[JochenFromm]

As a workaround you can try to install the old version 0.2.2

%pip install keplergl==0.2.2

[camilaagw]

Hi,
While the issue is solved, is there any way to access the config using the console tab in the Chrome developer tools?
In the Console, I found the method window.KeplerGl.KeplerGlSchema.getConfigToSave(<state>), however, I cannot find the variable that defines the current state of the visualisation.

[camilaagw]

@ramayer-fli just for my own knowledge, how do you get the config in Jupyter Lab?

[MilheiroSantos]

I just got the exact same issue. I was able to get the config by executing, in another notebook cell:

# if `map` is the KeplerGl instance
map.config

[MilheiroSantos]

I've submitted a pull request that clarifies the new method of getting the config #2697. From my side, once the documentation is clarified and there is a workaround to the {} button, we could close this bug.