Workaround for "Exception in template helper: idStringify after update to newest core package versions" #33
Conversation
This file contains hidden or 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
dr-dimitru
added a commit
that referenced
this pull request
Sep 10, 2017
- Hot fix for #32, see #33 and [meteor/#9060](meteor/meteor#9060), thanks to @jankapunkt - Dependencies update - Overall fixes - Compatibility with `[email protected]`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As described in #32 there is a problem with id values for findOne in newest minimongo.
Please check, if can even reproduce the error. If you can't reproduce, then this PR is not of use.
I couldn't track back, whether the error is caused by ostrio:files' findOne implementation or minimongo's internals.
However, when not using _id values, such as false or "" then there is no error thrown and the behavior is restored.