Remove/update old calls to Meteor.flush() #236
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edemaine
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #235. Some calls to
Meteor.flush()(in events) seemed unnecessary, while other calls toMeteor.flush()were actually needed (to upgrade the web UI according to session variables before trying to modify the contents) and replaced withTracker.flush(). Now no errors in my app.I've gone ahead and published my own fork which incorporates this PR as well as @TechplexEngineer's fixes. You can use it via
meteor add edemaine:accounts-ui-bootstrap-3.