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.

Sign up for GitHub

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

Jump to bottom

feat: consider "public" and "private" user fields #3

Open
Regaez opened this issue Nov 8, 2017 · 0 comments
Open

feat: consider "public" and "private" user fields #3

Regaez opened this issue Nov 8, 2017 · 0 comments
Labels
feature

Comments

@Regaez
Copy link
Owner

Regaez commented Nov 8, 2017

Perhaps the UserResource object should not expose fields such as access or state... unless the request is authenticated for that user, or an admin?

We currently always filter out hashed_password so that it is not exposed publicly.
@Regaez Regaez changed the title Consider "public" and "private" user fields fix: consider "public" and "private" user fields Aug 7, 2019
@Regaez Regaez changed the title fix: consider "public" and "private" user fields feat: consider "public" and "private" user fields Aug 7, 2019
@Regaez Regaez added the feature label Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Regaez