Open ilan-gold opened 6 months ago
While I agree it may not be the nicest API, without more context/motivation, I don't think there is enough to justify this breaking change, as it will break existing docs/reference materials, Vitessce config generation code in portal-visualization
package, and notebooks that are being used in HuBMAP workspaces that rely on the VitessceConfig.to_python
function
@keller-mark This is motivated by https://github.com/vitessce/vitessce-python/pull/333. We could just keep the non-outward-facing changes so that when the SpatialDataWrapper
calls "private" attributes, they have better names.
Open to other options here, but basically I did two things.
adata_XXX
->base_XXX
since the semantics are a bit more general and I thinkadata
is redundant anywaypath
->elem
since I thinkelem
is a bit nicer andpath
can refer to a sub-URL which is kind of a path, but also not really.This is definitely a breaking change, so I'm going to try to finish up other PRs that are also breaking at the same time, like our python support.