github/meteor
1
1
Fork 0
mirror of https://github.com/meteor/meteor.git synced 2026-05-02 03:01:46 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated History.md with #10469 improvements

Browse Source 
including new Meteor.user() options parameter and Accounts.config({defaultFieldSelector...})
This commit is contained in:
wildhart
2019-12-19 01:46:52 +13:00
committed by GitHub
parent c7df650064
commit 97b2ef8b86
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
History.md
View File

@@ -1,5 +1,20 @@
## v.NEXT
* `Meteor.user()`, `Meteor.findUserByEmail()` and `Meteor.findUserByUserName()` can take a new
`options` parameter which can be used to limit the returned fields. Useful for minimizing
DB bandwidth on the server and avoiding unnecessary reactive UI updates on the client.
[Issue #10469](https://github.com/meteor/meteor/issues/10469)
* `Accounts.config()` has a new option `defaultFieldSelector` which will apply to all
`Meteor.user()` and `Meteor.findUserBy...()` functions without explicit field selectors, and
also to all `onLogin`, `onLogout` and `onLoginFailure` callbacks. This is useful if you store
large data on the user document (e.g. a growing list of transactions) which do no need to be
retrieved from the DB whenever you or a package author call `Meteor.user()` without limiting the
fields. [Issue #10469](https://github.com/meteor/meteor/issues/10469)
* Lots of internal calls to `Meteor.user()` without field specifiers in `accounts-base` and
`accounts-password` packages have been optimized with explicit field selectors to only fetch
the fields needed by the functions they are in.
[Issue #10469](https://github.com/meteor/meteor/issues/10469)
## v1.8.1, 2019-04-03
### Breaking changes