Accounts.forgotPassword callback with an error message"User not found [403]" if the user with the specified email does not exist.

Is it possible to stop this error message from reaching the client ? If not is it something that should be changed ? I can make a PR to address this.

Description:

Whenever I change any of the room info (description, announcement, etc.) this resets the room setting which is supposed to hide system messages.

Steps to reproduce:

1. Go to "Room info" in a channel where you have privileges to change the room info.
2. Toggle on the "Hide system messages" setting. Confirm that this change itself is not posted in the channel.
3. Close

Just gave VulcanJS a try after using Meteor for a while. I'm getting the following error:

`
Warning: React.createFactory() is deprecated and will be removed in a future major release. Consider using JSX or use React.createElement() directly instead.
meteor://💻app/packages/vulcan_lib.js:422
if (error) throw error; // eslint-disable-next-line no-console
^

[Error:

When errors are returned (If the input information is incorrect) , The name of the corresponding collection is also in the error message . LIKE this :

name is required in CollectionName insert

i want this part (in CollectionName insert ) gone.

error messages belong to software users, and users do not need to see the name of the collection.
And this part should not be returned at all.

https://github.com/Meteor-Community-Packages/meteor-roles/blob/32c230ded9cb92b27a3485d143cabf2732fef186/roles/roles_common.js#L543-L557

The function _getInheritedRoleNames() is currently used to construct the array inheritedRoles on a role-assignment, where it only takes over the parameter _id. If you have data stored on the role, wouldn't it be better to have it copied along?

If one o

I am modifying the modifier passed into a before.update hook and noticed that these changes are being passed to the update hook on the server. So the client and the server aren't processing the same modifier; the server only has the modifier outputted by the client side hook. This is related to the discussions here https://forums.meteor.com/t/meteor-collection-hooks-confused/748/7.

The solution

Please add a sign up button to main page.

I'd love to see the UserAgent string broken down into more fields. This would allow a developer to easily write queries and aggregations based on the different parts of the string. I'd love to use this to see how many users are on a particular platform. But right now this is difficult because if a user happens to use safari/601.1 and another uses safari 600.1, these strings are considered separate