Using individual Vitessce components #1232
Replies: 1 comment 1 reply
-
Hi @davehorsfall, thanks for reaching out. While not documented, it is possible to render individual components. We currently export the Heatmap, Scatterplot, and Spatial components from the root We also currently generate JS bundles for each component individually, and I am aware of one group using these bundles (@alexvpickering, @ivababukova) There are two main reasons why we haven't documented these:
Since we have several major planned features on our roadmap I wouldn't want to commit to not making any breaking changes to internal props. I understand that you have a different use case, but one benefit of using the JSON configuration is that we can prevent most breaking changes by automatically upgrading the configuration across different JSON configuration schema versions. All of that being said, if you wanted to go ahead and use the internal components, then I would suggest:
We also recently merged support for plugins which are another way that you could go beyond the current features of Vitessce for a more custom use case. This will be included in the |
Beta Was this translation helpful? Give feedback.
-
We've been working with Vitessce for several months with some great successes. Thanks for developing and sharing. I wanted to ask if it is possible (and supported) to render individual components? For example, when working with Vitessce in React, and based on a configuration, can we insert the
<scatterplot>
component or the<spatial>
component directly?We've noted that the usage docs of an older version at npm, suggest this is possible. However, I can't find any clear information on what props are needed for each component, and how to generate those values based on a defined configuration.
We're basically seeking to have more granular control of the components and layout, without using the
VitessceGrid
.Apologies if I've misunderstood something, and thanks for any help.
Beta Was this translation helpful? Give feedback.
All reactions