Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [BUG]: Not possible to easily extract offending edge/node ID from VueFlowError #1276

Closed
1 task done
snoozbuster opened this issue Feb 1, 2024 · 0 comments
Closed
1 task done
Assignees
Labels
bug Something isn't working triage Awaiting triage

Comments

@snoozbuster
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues and this is a new bug.

Current Behavior

When a VueFlowError is instantiated, a reference to the offending edge ID is passed. This is used to generate an error message but the value itself is not stored on the error, either in a custom property or in the cause property of the error. This makes string parsing the only way to extract the offending edge/node/etc, instead of simply accessing it off the error object, which makes error handling of the type mentioned in this comment quite challenging/error-prone.

Expected Behavior

The error should expose all relevant information for programmatic access.

Steps To Reproduce

  1. Trigger any EDGE_INVALID error and observe the resulting error.

Relevant log output

No response

Anything else?

No response

@snoozbuster snoozbuster added bug Something isn't working triage Awaiting triage labels Feb 1, 2024
Repository owner locked and limited conversation to collaborators Feb 1, 2024
@bcakmakoglu bcakmakoglu converted this issue into discussion #1277 Feb 1, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Something isn't working triage Awaiting triage
Projects
None yet
Development

No branches or pull requests

2 participants