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
If no trigger matching configured name is found an error is logged, nil trigger is returned and handled by the SDK.
If an error is encountered when intiializing a custom trigger, an error is logged before panicking. I think in case of these errors it makes sense to force returning nil (even if the function returned a trigger and an error) and let the SDK handle it like it would any other nil trigger situation.
The text was updated successfully, but these errors were encountered:
If no trigger matching configured name is found an error is logged, nil trigger is returned and handled by the SDK.
If an error is encountered when intiializing a custom trigger, an error is logged before panicking. I think in case of these errors it makes sense to force returning nil (even if the function returned a trigger and an error) and let the SDK handle it like it would any other nil trigger situation.
The text was updated successfully, but these errors were encountered: