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
The docstring says:
@returns {Observable<{numberAffected, insertedId}>} Observable which completes with an * Object that contain the keys numberAffected and insertedId.
However the return value is let obs = this._createObservable<number>(observers);
let obs = this._createObservable<number>(observers);
So either there is a bug in the documentation or in the implementation.
Edit:
So The original Meteor Collection.upsert() function actually returns {numberAffected, insertedId} directly instead of in the callback.
{numberAffected, insertedId}
The text was updated successfully, but these errors were encountered:
InsertedId is what makes upsert worthy , no sense to drop it and return only the number of affected rows. Any progress with this one?
Sorry, something went wrong.
No branches or pull requests
The docstring says:
@returns {Observable<{numberAffected, insertedId}>} Observable which completes with an * Object that contain the keys numberAffected and insertedId.
However the return value is
let obs = this._createObservable<number>(observers);
So either there is a bug in the documentation or in the implementation.
Edit:
So The original Meteor Collection.upsert() function actually returns
{numberAffected, insertedId}
directly instead of in the callback.The text was updated successfully, but these errors were encountered: