Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for new feature in 3.17 allowing cloning published visualisations? #77

Open
aendra-rininsland opened this issue Jan 17, 2022 · 2 comments

Comments

@aendra-rininsland
Copy link

I was going through the release notes and noticed how in 3.17.0, the SDK now allows:

...published visualisations to be cloned into the SDK

How does this work? It sounds really interesting, but AFAICT isn't documented anywhere.

I looked through the commit for that version and this was the only thing in it that seemed to be related to that functionality?

@oampo
Copy link
Contributor

oampo commented Jan 18, 2022

Hey @Aendrew! Nice spot - this feature is a little bit hidden away, but we're working on a docs update.

The idea behind the feature is to make it easier for template authors to debug issues with visualisations in production by being able to clone the data and settings into the SDK. So if you have a published visualisation for a particular template, you should be able to start the SDK, and then visit http://localhost:1685/#ID (replacing ID with the ID of the visualisation, which you can take from the end of the published URL - for example http://localhost:1685/#12345678). That will go and fetch the data and settings, and copy them over into the SDK without you needing to manually reproduce the settings or edit the data files.

This isn't very well tested yet, so YMMV, but hopefully it's helpful if you need to do some template debugging.

@aendra-rininsland
Copy link
Author

@oampo That's really interesting! Thanks for getting back to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants