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
Not sure if I'm mistaken about this, but take the comments module for example.
action/comments.js sets LocalState for errors in both the Meteor.call for posts.createComment as well as outside the Meteor.call.
If you throw an error in the server-side action for posts.createComment, the error isn't displayed.
If you throw an error in action/comments.js before the Meteor.call, it is.
If you comment out return clearErrors in the corresponding container, the error set inside the Meteor.call callback is displayed, but is not cleared when you navigate to another page and then come back, it will only disappear if you hard reload.
Would this be because Meteor.call is asynchronous? What would be the best way of handling error (and success) messages set in the Meteor.call callback?
The text was updated successfully, but these errors were encountered:
Hi,
Not sure if I'm mistaken about this, but take the comments module for example.
action/comments.js
sets LocalState for errors in both theMeteor.call
forposts.createComment
as well as outside theMeteor.call
.posts.createComment
, the error isn't displayed.action/comments.js
before theMeteor.call
, it is.return clearErrors
in the corresponding container, the error set inside theMeteor.call
callback is displayed, but is not cleared when you navigate to another page and then come back, it will only disappear if you hard reload.Would this be because
Meteor.call
is asynchronous? What would be the best way of handling error (and success) messages set in theMeteor.call
callback?The text was updated successfully, but these errors were encountered: