-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Add AbuseTypes CRUD #275
Comments
@maebeale any feelings about using https://github.com/thoughtbot/administrate for admin CRUD stuff? I've used it in the past and have really enjoyed how easy it made admin to setup. |
Hey there, @austenmadden ! Thanks for asking about this. We'd decided to roll our own CRUD for this project. |
@austenmadden would you like to be assigned to this issue? |
Sounds great, @austenmadden ( and @eluthern )! |
We have the db, but need to add CRUD views so Admin user can add/edit/delete abuse_types
AbuseType policy should require a new Permission constant, called SYSTEM_SETUP, for all AbuseType actions, with the following exception:
AbuseTypesController needs to still service the json call (but change it to a different endpoint than the index, to help with the permission policy) from the /requesters/new form. This endpoint should not require ANY permissions, bc it'll get called from an unauthenticated user. So, it needs to get changed on the React side, added to the routes, and added to the AbuseTypesController.
The text was updated successfully, but these errors were encountered: