Hi all. Had a quick question on coding patterns for expectations.
Suppose I have a data verification step within a solid which should be treated as terminal or non-terminal, depending on the configuration of the pipeline (eg., maybe in dev mode, all failed expectations are terminal, whereas in production runs a failed expectation is only recorded).
I can obviously write code that either raises a Failure or yields an ExpectationResult based on the mode that pipeline is running in. Just wondering if there is already API for doing that that I'm overlooking?