chore(docs): cleanup

This commit is contained in:
braks
2024-06-20 09:02:19 +02:00
parent 3ca9aca72b
commit e94e0e879c
4 changed files with 3 additions and 11 deletions

View File

@@ -22,7 +22,7 @@ const downloadCountTransitioned = useTransition(downloadCount, {
})
starGazersCount.value = 3000
downloadCount.value = 50000
downloadCount.value = 150000
Promise.all([
$fetch('https://api.github.com/repos/bcakmakoglu/vue-flow?page=$i&per_page=100').then((data) => {

View File

@@ -79,8 +79,6 @@ function logEvent(name, data) {
}
</script>
# Introduction to Edges
Edges are the links connecting your nodes, forming a map.
Each edge runs from one handle to another, and can be customized to your liking.

View File

@@ -50,8 +50,6 @@ function logEvent(name, data) {
}
</script>
# Introduction to Nodes
Nodes are the underlying components of your graph.
They can be any kind of data you want to visualize in your graph, existing independently and being interconnected
through edges to create a data map.

View File

@@ -1,7 +1,5 @@
# State
## Introduction
Under the hood Vue Flow uses [Provide/Inject](https://v3.vuejs.org/guide/component-provide-inject)
to pass around it's state between components.
You can access the internal state through the [`useVueFlow`](/guide/composables#usevueflow/) composable.
@@ -12,13 +10,11 @@ an already existing store from the current context.
Internal state can be manipulated, for example by adding new elements to the state. The
state is reactive and changes will be reflected on the graph.
```vue{4-6}
```vue
<script setup>
import { useVueFlow } from '@vue-flow/core'
const { getNodes, onPaneReady } = useVueFlow({
... // you can pass any VueFlowProp to the composable as a static option
})
const { getNodes, onPaneReady } = useVueFlow()
// event handler
onPaneReady((i) => i.fitView())