You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People can forget to change them.
And I think scaffolding only the allow method sufficient. I usually add deny methods in very specific parts of my project.
The text was updated successfully, but these errors were encountered:
Just realized the default allow/deny rules allows anyone full write access to the DB. I totally assumed it was the opposite. Having these rules is like adding the "insecure" package twice...
I vote for changing this. It should be locked down by default and then the developer can gradually open up access as needed.
My take is, while Meteors 'insecure' package is for playing around and get an app up and running quickly, I think by the time a developer start to use/need EM it is probably already writing production code. And thus the first thing you do is to remove insecure and autopublish. My 2 cents.
People can forget to change them.
And I think scaffolding only the allow method sufficient. I usually add deny methods in very specific parts of my project.
The text was updated successfully, but these errors were encountered: