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
In the pre-NoFlo version of .fbp notation, connection capacity was indicated by a number in brackets immediately following the arrow (->). NoFlo JSON has no provision for connection capacity AFAIK, although @bergie has suggested using metadata within the component part of a process specification.
Sorry, I've been out all day, and have to head out again! Looks like connection metadata in the JSON is shaping up to be keyword-based, so I'm easy about how to encode capacity... :-)
In the pre-NoFlo version of .fbp notation, connection capacity was indicated by a number in brackets immediately following the arrow (
->
). NoFlo JSON has no provision for connection capacity AFAIK, although @bergie has suggested using metadata within the component part of a process specification.Refs: noflo/noflo-ui#371, noflo/noflo-ui#370, jonnor/javafbp-runtime#2
The text was updated successfully, but these errors were encountered: