Delete the name of collections in error messages about meteor-collection2

[copleykj]

I'm not sure this is an issue.. These error messages should never be seen by the user. Errors should be caught, handled in application code, and custom error messages propagated to the UI.

[StorytellerCZ]

Probably good to leave for development and get rid of it in production.

[StorytellerCZ]

That might be so, but with Meteor it is easy to do error.message in method callback and just return that, so it is probably too common (I'm guilty of this as well). But if your error handling depends on string parsing with the collection name then this would be a breaking change...

[Saeeed-B]

@copleykj @StorytellerCZ
This is exactly the problem, we can easily show the exact error to the user, and more importantly, this error is in any language we want.
And when we show these messages to the user, there is no need for many additional validations.
Please look at the error system in Laravel, they take the user field and if it does not match any of the credentials, they show the message corresponding to the same credential.
If we can make the validation only in the collection is great, because it no longer matters where the input comes from, in any case it must have the necessary validity.
Also, if it is not valid, a very accurate message will be displayed.
I hope I was able to get it right, because I do not speak English very well

[StorytellerCZ]

I think the compromise might be that on production the collection name will be hidden while we leave it as is for development.