Delete the name of collections in error messages

[Saeeed-B]

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

[github-actions[bot]]

Thank you for submitting an issue!

If this is a bug report, please be sure to include, at minimum, example code showing a small schema and any necessary calls with all their arguments, which will reproduce the issue. Even better, you can link to a saved online code editor example, where anyone can immediately run the code and see the issue.

If you are requesting a feature, include a code example of how you imagine it working if it were implemented.

If you need to edit your issue description, click the [...] and choose Edit.

Be patient. This is a free and freely licensed package that I maintain in my spare time. You may get a response in a day, but it could also take a month. If you benefit from this package and would like to see more of my time devoted to it, you can help by sponsoring.

[Saeeed-B]

@intrueder @coagmano @SachaG @SimonSimCity @tophsic I really tried every inventory method, but this problem was not solved. And I have been involved in it for many days. Please Guide me

[Saeeed-B]

@aldeed The documentation is not really clear

[coagmano]

@Saeed-Bahrami Try using defineValidationErrorTransform to customise the message and details sent to the client. See https://github.com/aldeed/simpl-schema#customize-the-error-that-is-thrown

Which version of simpl-schema are you using?

[Saeeed-B]

@coagmano im using: "simpl-schema": "^1.10.1",

[Saeeed-B]

@Saeed-Bahrami Try using defineValidationErrorTransform to customise the message and details sent to the client. See https://github.com/aldeed/simpl-schema#customize-the-error-that-is-thrown

That is, to manually separate and delete the names of collections?

[Saeeed-B]

However, 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

[coagmano]

I don't pass collection insert/update/etc messages to the client at all. So I agree with you there. The solution then is to not return the error to the client

I do validation separately on the client, so the message is relevant to the specific input or action that caused the error

[Saeeed-B]

@coagmano It is true. But for more security and reliable work. The input of collections should also be controlled. And how much better to do client (Components) and server (Collections) authentication together (with Collection2)

[Saeeed-B]

@Saeed-Bahrami Try using defineValidationErrorTransform to customise the message and details sent to the client. See https://github.com/aldeed/simpl-schema#customize-the-error-that-is-thrown

I used exactly this method to convert error to meteor error. Both server (in Start Up ) and client side. But it didn't really work!

[SachaG]

@Saeed-Bahrami it's not great manners to mention people completely unrelated to an issue. I also have work to do, asking me to provide free support on a project that isn't even mine feels a bit too much…

[Saeeed-B]

@SachaG Sorry, I thought these people were related.

[aldeed]

@Saeed-Bahrami This error comes from the collection2 package, which is maintained in a different repo: https://github.com/Meteor-Community-Packages/meteor-collection2/blob/master/package/collection2/collection2.js#L479

Please submit an issue on that repo instead.