Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why we need to call restrict!? #58

Open
kelvinst opened this issue Nov 19, 2014 · 0 comments
Open

Why we need to call restrict!? #58

kelvinst opened this issue Nov 19, 2014 · 0 comments

Comments

@kelvinst
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant