Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handling removed nodes/edges and constraints #33

Open
fiannaca opened this issue Jun 2, 2015 · 1 comment
Open

Handling removed nodes/edges and constraints #33

fiannaca opened this issue Jun 2, 2015 · 1 comment
Assignees
@sonyaa

Comments

@fiannaca
Copy link
Contributor

fiannaca commented Jun 2, 2015

What should we do when an edge or node is removed that was satisfying a constraint on another node it was connected to?
@sonyaa
Copy link
Contributor

sonyaa commented Jun 2, 2015

But don't we only check those kinds of constraints at some specific point in time (most likely when user clicks "validate" or "download" or something like that)? Or we check them for autosuggest - but that's also done on user click, not all the time in the background.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sonyaa sonyaa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fiannaca @sonyaa