[Feature Request] Programmatic Export/Save of visConfig JSON

[noamanemobidata]

It would be helpful to add a function that allows users to programmatically export or save the visConfig JSON.

[bruceyyu]

This is not easy to implement. As we are using htmlwidget in R to render GWalkR's core HTML app, we are unable to get the real-time update of the visConfig from the HTML in R environment due to the lack of bi-directional communication.

[noamanemobidata]

A common use case involves saving visualizations (the json config) so that they can be easily accessed and reviewed later, without the need to recreate them each time.

[bruceyyu]

@noamanemobidata actually you can press this button to download the JSON config file

[noamanemobidata]

Yes, but we want to do this programmatically : save and restore visualizations, especially in interactive applications such as Shiny. The goal is to enable users to save their current visualization as a JSON (e.g., in a database or S3 storage) with a "Save Viz" button, making it easy to restore the visualization state later.