Releases: dash14/v-network-graph
Releases · dash14/v-network-graph
v0.9.18
Bug Fix
- Fixed a problem that changes to the
fixed
property of the node position were not reflected in the network graph using d3 force-layout.
v0.9.17
Bug Fixes
- Fixed import error when running vue-tsc on a project containing v-network-graph. (#156)
v0.9.15
Bug Fix
- Fixed path drawing not being updated when
edges
in path prop are updated. (#143)
v0.9.14
Bug Fix
- Fixed not using the specified node position when restoring a deleted node. (#137)
v0.9.13
Bug Fix
- Fixed incorrect zoom value calculation results in some cases when
"fit-content"
was specified in configs.view.autoPanAndZoomOnLoad
.
The v0.9.12 is missing because it was found that more corrections were needed after the "v0.9.12" was tagged.
v0.9.11
Features
- Supported for fitting graphs to the edge of the display area.
- There are two ways to do this:
- Specify the configs as follows
const configs = defineConfigs({
view: {
autoPanAndZoomOnLoad: "fit-content",
fitContentMargin: 0, // default: "8%"
}
};
- Specify as an argument to
fitToContents()
method
const graph = ref<VNetworkGraphInstance>();
// ...
graph.value?.fitToContents({ margin: 0 });
- See below for details, including the format of the values that can be specified:
v0.9.10
Bug Fix
- Fixed an error when calculating a curve with two nodes in the same position by @hpawa in #134 (Issue #133) 😍
v0.9.9
Bug Fix
- Fixed incorrect start node determination for paths (#131)
- If more than two of the same edge were consecutive, the determination of the starting point could be incorrect.
v0.9.8
Bug Fix
Performance improvement:
- Fixed to not render uselessly when VEdgeOverlay is not used by @zamplyy in #129 (Issue #130) 😍