Until now I have just been using meteor audit argument checks package and doing my own server side validation I’m now looking at the collection2 package and simple schema package.
I really like the collection2 package but don’t believe in having the client create a collection but just have the client call a meteor method and the server create the db collection. Also related to “Meteor Methods vs Client-Side Operations”
I know you can you call the collection2 insert method on the server (not sure there is a point this if you’re already doing it via meteor method call) but then you can’t add anything custom for example if I want to add a createdDate or add the userId. (I might be missing something here I know you can do function calls inside the schema)
So I was just looking at using simple schema package just for the server side validation however isn’t this the same as just having the audit argument checks package?