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
Copy file name to clipboardExpand all lines: docs/src/guide/troubleshooting.md
+19-12Lines changed: 19 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,27 +101,34 @@ const edges = ref([
101
101
102
102
## Evaluating Errors During Runtime
103
103
104
-
During development, Vue Flow emits warnings to the console for errors encountered. These warnings are intended to help developers identify and resolve issues without failing silently. In production, however, these warnings are suppressed to avoid exposing potentially sensitive information to end users.
104
+
During development, Vue Flow emits warnings to the console for errors encountered.
105
+
These warnings are intended to help developers identify and resolve issues without failing silently.
106
+
In production, however, these warnings are suppressed.
105
107
106
-
### Hooking into onError or @error Events
108
+
### Handling Errors
107
109
108
-
You can handle errors programmatically by hooking into the `onError` or `@error` events. This allows you to perform custom operations based on the type of error encountered. Here's an example of how to use `isErrorOfType` to handle a specific error type:
110
+
You can handle errors by hooking into the `onError` event.
111
+
This allows you to perform custom operations based on the type of error encountered.
112
+
Here's an example of how to use the `isErrorOfType` utility to handle an error of `NODE_INVALID` type.
0 commit comments