Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Picking up from #389
I'm almost done with this but it still feels lacking. Using the
PUT
method to cancel invites is just lazy (sorry), but the alternative is to refactor all API calls to use proper Form Actions.I'm mostly inclined to do a refactoring on the whole user model and add some proper ACL.
Changes so far
Changing the user role seems too much hassle, thus the workaround is to remove and re-add him with the new role.
ACL Proposal
admin
column to theusers
table and drop theserver_members
What do you think?