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
As it stands right now, developers tend to use control outputs to indicate errors which can lead to simply connecting these error control outputs to the node in question and the nodes using it. It would be much cleaner to define these error control outputs which would only add the behavior of them implicitly bubbling up to the nodes higher up in the dependency hierarchy. This can be further customized by allowing the developer to make exceptions for some error control outputs and handle these as they would otherwise have as a normal control output.
Bonus utility: adding error data to the control output for debugging purposes.
Example of how this can make logic unnecessarily complicated.
The text was updated successfully, but these errors were encountered:
As it stands right now, developers tend to use control outputs to indicate errors which can lead to simply connecting these error control outputs to the node in question and the nodes using it. It would be much cleaner to define these error control outputs which would only add the behavior of them implicitly bubbling up to the nodes higher up in the dependency hierarchy. This can be further customized by allowing the developer to make exceptions for some error control outputs and handle these as they would otherwise have as a normal control output.
Bonus utility: adding error data to the control output for debugging purposes.
Example of how this can make logic unnecessarily complicated.
The text was updated successfully, but these errors were encountered: