-
Notifications
You must be signed in to change notification settings - Fork 177
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
useSchema should export a "disconnect" function to programmatically disconnect two linked nodes #31
Labels
enhancement
New feature or request
feature request
Request for a new feature
good first issue
Good for newcomers
Milestone
Comments
antonioru
changed the title
Disconnect function
useSchema should export a "disconnect" function to programmatically disconnect two linked nodes
Nov 13, 2020
antonioru
added
enhancement
New feature or request
feature request
Request for a new feature
good first issue
Good for newcomers
labels
Nov 13, 2020
ginoemiliozzi
added a commit
to ginoemiliozzi/beautiful-react-diagrams
that referenced
this issue
Nov 25, 2020
Hello! I've raised this PR to address this. |
ginoemiliozzi
added a commit
to ginoemiliozzi/beautiful-react-diagrams
that referenced
this issue
Nov 25, 2020
antonioru
added a commit
that referenced
this issue
Nov 26, 2020
Add disconnect function exported in useSchema hook - #31
Thank you @ginoemiliozzi !!! |
Open
This will be solved when the #70 will be released |
Lindsay89
pushed a commit
to Lindsay89/beautiful-react-diagrams
that referenced
this issue
Dec 14, 2020
useSchema.ts needs to disconnect too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
feature request
Request for a new feature
good first issue
Good for newcomers
Given that
useSchema
currently exports aconnect
function to connects two different nodes and aremoveNode
function to remove a given node, it should also export adisconnect
function to programmatically disconnect two linked nodes without removing them.At the moment the only way to do so, is to change the schema directly.
The text was updated successfully, but these errors were encountered: