Deprecate bypassSchema param, introduce updateOptions #19
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 reported in #15,
bypassSchema
parameter is not working.I've taken here a different approach, you can now pass
updateOptions
object to cache config.Instead of
we have
which works as expected.
Other updates:
cacheField
transform can now returnundefined
without crashing, because Meteor changed the way undefined fields are handled in insert/update/find. See the docslodash
version to 4.17.15updateOptions
which requires bothaldeed:collection2
andsimpl-schema
packages