search

inossidabile / protector

Comfortable (seriously) white-list security restrictions for models on a field level
MIT License
270 stars 31 forks source link

Why we need to call restrict!? #58

Open kelvinst opened 9 years ago

kelvinst commented 9 years ago

So, there is a way to avoid the need to call retrict! everytime I want to access the retricted scope and model instances?

I think that (if it's not) this will be veeery good, since whitelisting things is pretty more confortable when you don't need to remember to call the whitelisted option.