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
Hi! I'm trying out the new Streaming feature, and it seems like there are some inconsistencies between the types and the actual behavior.
The callback to stream events seems to be called with just the event object as the first argument, and the event object along with the transaction id and event type as the second argument.
Thank you for creating the issue. Types improving is on our road map. Meanwhile, I created a ticket for this bug and our project manager will prioritize it.
we track it internally as DRV-561
Hi! I'm trying out the new Streaming feature, and it seems like there are some inconsistencies between the types and the actual behavior.
The callback to stream events seems to be called with just the event object as the first argument, and the event object along with the transaction id and event type as the second argument.
faunadb-js/src/stream.js
Line 210 in 3f07a6f
However, the types indicate that the first argument is the event type, followed by the transaction id, and finally the event object.
faunadb-js/src/types/Stream.d.ts
Lines 24 to 33 in 3f07a6f
The text was updated successfully, but these errors were encountered: