meteor-collection2

Full Changelog: https://github.com/Meteor-Community-Packages/meteor-collection2/compare/4.0.1...4.0.2-beta.1

What's Changed

• fix: use actually dynamic import in dynamic.js by @jankapunkt in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/450

Full Changelog: https://github.com/Meteor-Community-Packages/meteor-collection2/compare/4.0.0...4.0.1

What's Changed

• Update README.md by @Prinzhorn in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/435
• feature(ci): add comment issue workflow by @jankapunkt in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/442
• Add CodeQL workflow for GitHub code scanning by @lgtm-com in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/441
• Support for asynchronous mongo methods by @klablink in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/443
• Meteor 3.0 migration by @harryadel in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/444

Breaking

• You no longer need to install simpl-schema as we from now on use the Meteor package aldeed:simple-schema again, which is now under our maintenance. While the npm package works, there will be no Meteor support in the future and we decided for a hard fork in order to remain compatible.
• Collection2 is now optionally dynamic OR static imported. This allows to reduce client bundle size.

In order to import it dynamically you need to run:

import 'meteor/aldeed:collection2/dynamic'

Collection2.load() // returns a promise!!!!

In order to import it statically you need to run:

import 'meteor/aldeed:collection2/static'
Collection2.load() // no promise

New Contributors

• @Prinzhorn made their first contribution in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/435
• @lgtm-com made their first contribution in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/441
• @klablink made their first contribution in https://github.com/Meteor-Community-Packages/meteor-collection2/pull/443

Full Changelog: https://github.com/Meteor-Community-Packages/meteor-collection2/compare/3.5.0...4.0.0

Add the ability to override in-built schema clean options.

• Make compatible with Meteor 2.3

• Code modernization in few places
• You can now set packages.collection2.disableCollectionNamesInValidation in your Meteor settings to disable showing Collection name in errors from server, this is set to false by default to preserve the original behavior. (fixes #422)
• Moved from CircleCI testing to GitHub actions

• Force raix:[email protected] and tmeasday:[email protected]

• Allow tmeasday:check-npm-versions to use version 1.0.1 as well

• Added multiple schemas feature
• Updated dependencies
• Updated Meteor version
• Updated tests

• Added pick and omit feature
• Updated dependencies
• Updated tests
• Added GitHub templates for issues and PRs.

No changes, but aldeed:collection2 is now a shell package that installs three component packages: aldeed:collection2-core, aldeed:schema-index, and aldeed:schema-deny

• Fixed an issue where an accidental breaking change in SimpleSchema v1.4.0 caused denyInsert and denyUpdate to stop working. If using SimpleSchema v1.4.0 or higher, be sure to use Collection2 v2.7.1 or higher.
• Fix upsert validation when _id is required in the schema
• Throw a clearer error for when all keys are removed from the document or modifier during filter cleaning

Even if you skip all validation and cleaning, Collection2 will still do some object parsing that can take a long time for a large document. To bypass this, you can now set the bypassCollection2 option to true when you call insert or update. This works only in server code.

• docId is now set in the autoValue and custom contexts for inserts, too, if possible
• The validationContext option can now be a reference to a context instead of a string name

• Validation and cleaning is no longer duplicated when using the upsert method instead of {upsert: true} option.
• Added sparse option which can be set to true along with index option to force a sparse index

Use latest simple-schema version

• Properly set docId in autoValue and custom contexts when provided as non-object. (Thanks @FatBoyXPC)
• Update SimpleSchema package dependency version

Fix handling of _id property on client to match server.

You can now pass an extendedCustomContext option when calling insert or update. Set this to an object that will be used to extend this within any custom validation functions that are called.

You can now pass an extendAutoValueContext option when calling insert or update. Set this to an object that will be used to extend this within any autoValue functions that are called.

Note that the extendedCustomContext and extendAutoValueContext options will work fine for calls in server code or calls against local (unmanaged) collections in client code, but they will not work with calls against normal (managed) collections in client code. When the second round of validation happens on the server, your custom contexts will not be set.

Also: When a validation error is passed to the insert or update callback, error.validationContext is now set to the validation context that was used.