Optionalargs: Subset<T, TSCustomMessage$buttonsArgs<ExtArgs>>Attaches a callback for only the rejection of the Promise.
Optionalonrejected: null | ((reason: any) => TResult | PromiseLike<TResult>)The callback to execute when the Promise is rejected.
A Promise for the completion of the callback.
Optionalargs: Subset<T, TSCustomMessage$embedArgs<ExtArgs>>Attaches a callback that is invoked when the Promise is settled (fulfilled or rejected). The resolved value cannot be modified from the callback.
Optionalonfinally: null | (() => void)The callback to execute when the Promise is settled (fulfilled or rejected).
A Promise for the completion of the callback.
Attaches callbacks for the resolution and/or rejection of the Promise.
Optionalonfulfilled: null | ((value: T) => TResult1 | PromiseLike<TResult1>)The callback to execute when the Promise is resolved.
Optionalonrejected: null | ((reason: any) => TResult2 | PromiseLike<TResult2>)The callback to execute when the Promise is rejected.
A Promise for the completion of which ever callback is executed.
Optionalargs: Subset<T, TSCustomMessage$twitchStreamerArgs<ExtArgs>>Optionalargs: Subset<T, TSCustomMessage$webhookArgs<ExtArgs>>
The delegate class that acts as a "Promise-like" for TSCustomMessage. Why is this prefixed with
Prisma__? Because we want to prevent naming conflicts as mentioned in https://github.com/prisma/prisma-client-js/issues/707