We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to the insert() documentation:
insert()
Documents in changes for which an error occurs (such as a key conflict) will have a third field, error, with an explanation of the error.
changes
error
It seems that ValueChange currently lacks this in the type definitions.
ValueChange
The fix would seem to be very minor: simply add to ValueChange a third optional property, error.
The text was updated successfully, but these errors were encountered:
I couldn't reproduce this error field. tried listening to a table that got a conflict error and I got nothing in the "changes" feed...
Sorry, something went wrong.
I encountered the field during my use of forEach().
forEach()
To be clear, this is the changes field of an insert() result object.
Found it, returnChanges should be "always" for me to see it.
returnChanges
"always"
No branches or pull requests
According to the
insert()
documentation:It seems that
ValueChange
currently lacks this in the type definitions.The fix would seem to be very minor: simply add to
ValueChange
a third optional property,error
.The text was updated successfully, but these errors were encountered: