-
Notifications
You must be signed in to change notification settings - Fork 20
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
no visibility #167
Comments
this really touches on the data hierarchy we have. If we're going to call our top level postable thing Likeable, we need to pull the User owner and that sort of thing up to it. |
using the check annotation of the secure module is more about controllers that models. I think the best option is probably to just add visibility to likeable, as painful as that refactor might be. |
should we close this? |
Not quite yet. We still need to actually use the visibility in appropriate On Tue, Apr 24, 2012 at 9:36 PM, Amin Shali <
|
Right. |
need to implement some sort of visibility on all stuff.
The text was updated successfully, but these errors were encountered: