Open hluz opened 8 years ago
Having just read through that thread, it seems that Meteor is pretty far away from actually deprecating allow/deny.
With that said, file-collection contains its own allow/deny validation logic, and doesn't really heavily depend on Meteor's implementation. The insert
handler still registers with the underlying Meteor.Collection deny()
, but that could easily be switched-over to the same implementation pattern that remove
uses (overriding the default method handler).
Philosophically speaking I think allow/deny for HTTP read/write and Collection insert/delete make a lot of sense for file-collection.
I understand, and it was only heads-up in case you had some hard dependencies on it that would be difficult to change, prompted because in my newest application, the only use for allow/deny rules is for file-collection... Thanks for checking.
As discussed here: https://forums.meteor.com/t/proof-that-no-one-uses-allow-deny/23059/2 ...