-
Notifications
You must be signed in to change notification settings - Fork 116
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
how to limit attributes on resource? #99
Comments
We don't currently support explicitly including/excluding certain attributes during resource definition, but it's not a bad idea. If you don't want to do any work on the module itself the way to go today is to remove the attributes you don't want to expose with a milestone. If, on the other hand, you're interested in helping build out the feature: we already work with |
Ok. I am quite new to node, express and sequelize etc, but I gave it a shot: It now works as I wished and currently it only supports I also did no write any test but the existing tests ran without errors. If you have any suggestions for improvements, feel free to let me know. Thanks! |
@philotas thanks for the work! I'll pull it in presently and write a test or two for it. Are you sure that |
thanks! |
when I do a list or read, how do I limit the attributes to the one I want?
I don't want to send the password of a user to begin with.
I know I can specify the attributes when I include another resource, but what about the plain resource when read/list itself?
I am sure it has to be possible but I don't seem to be seeing it.
Or do I have to use a hook/milestone and delete the fields before sending? This seems to be the wrong approach.
thanks for your help!
The text was updated successfully, but these errors were encountered: