You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a read/write JSON-compatible structure for instantiating and "serializing" the configuration of a forcegraph
Motivation
Having a single, JSON-schema constrained description of a force graph's configuration would simplify a number of use cases.
Additionally, as JSON, it would be theoretically possible to create a mime renderer of a force graph, with this as the metadata. This might be a lower-touch way for other modules to emit a snaphshot of a graph.
Elevator Pitch
Provide a read/write JSON-compatible structure for instantiating and "serializing" the configuration of a forcegraph
Motivation
Having a single, JSON-schema constrained description of a force graph's configuration would simplify a number of use cases.
Additionally, as JSON, it would be theoretically possible to create a mime renderer of a force graph, with this as the metadata. This might be a lower-touch way for other modules to emit a snaphshot of a graph.
Design Ideas
This would allow for something like:
Under the hood these would map to the existing behaviors.
It should then also be possible to extract this back out.
Limitations
It would be challenging to extract de-referenced pointers to the behaviors: this could be somewhat fixed by one of:
behaviors
anOrderedDict
orInstanceDict
name
to each of the behaviors, and exposing them as a "squishy"@property
or other getter approach@T.validate
to ensure each has a unique nameThe text was updated successfully, but these errors were encountered: