As Pipes user I'd like to get more feedback from Pipes whether I have configured the blocks in my graph properly

[josvanroosmalen]

In order to make Pipes more "dummy"/"fool" proof, I want to work on a sanity checker, and one of the first things is a sanity checker during editing the graphs, e.g. check that Feature/Lookup has a valid cts.query.

During editing we need need to be able to validate properties/widgets/etc. Preferable the callback should be able to return "false" and then the editor should not be closed, and we need to be able to provide feedback via alert.

This ticket is not about implementing sanity checks itself, but only the callbacks. so that we can build sanity checking on this.

[sashamitrovich]

@josvanroosmalen, can we rephrase this as: "As Pipes user I'd like to get more feedback from Pipes whether I have configured the blocks in my graph properly"? Is this correct?

[josvanroosmalen]

yes

[danielholgate]

There are two different editing mechanisms in Pipes.
One is the native litegraph property editing, which opens a small black box:

The second are the editing screens which open up for blocks (current only three) via double click and are actually a window in the Pipes application rather than litegraph:

Capturing the second type of dialog is easy because are already Pipes code and can be captured during/before/after edit. The first type of property editing requires adding hooks into the litegraph framework

Need to confirm which properties are targeted in this ticket

[sashamitrovich]

yes

Thanks, I changed the title.