Files
meteor/packages
David Glasser 4777e64336 Don't pass server-generated _id to allow/deny
This lets you still use C.insert from the client but reject arbitrary
client-set _id's (as opposed to _id's generated using the Random.id()
algorithm with a client-determined _id).

If you don't want clients to be able to have any control over the _id at
all for inserts, then you'll have to forbid all direct inserts and use
your own methods which explicitly do `C.insert({_id: Random.id(), ...})`

Note that allow/deny rules with transforms still see an _id, because
transforms need to have (and preserve) _id.  This means that if you
really want to see the server-generated _id, you can just specify an
identity transform for your allow/deny rule.
2014-04-24 14:01:39 -07:00
..
2014-04-23 19:37:03 -07:00
2013-08-12 23:31:26 -07:00
2014-02-03 10:36:33 -08:00
OCD
2013-10-08 20:03:02 -07:00
2014-04-16 08:01:25 -07:00
2013-12-04 12:46:47 -08:00
2014-04-02 09:56:33 -07:00
2014-02-25 00:45:22 -08:00
2014-02-18 15:47:42 -08:00
2013-08-02 11:19:08 -07:00
2014-04-06 15:36:05 -07:00
2014-04-10 14:26:44 -04:00
2014-03-26 23:29:03 -07:00
2013-07-25 18:54:40 -07:00
2014-03-27 17:22:18 -07:00