Refactor API to separate deletes, removes, and locks from updates.

[dessalines]

Currently in the API, there isn't a separate endpoint / action for comment delete for example. A delete, is really a comment update, which sets an optional delete value in the form to True or False, and then sets the deleted column in the sql row. Same goes for lock, remove, etc.

It would be a good idea to separate these, both as separate API actions, and also create DB helper methods, which only update that specific column.

I still have to come up with all the actions that set simple booleans on the rows, but I think its

• Posts: delete, remove, lock, sticky.
• Comments: delete, remove, read
• Communities: delete, remove
• UserMention: read
• PrivateMessage: read, delete
• Users: This is good.

Comments from other thread:

A lot of API actions are currently Post edits, Comment edits, and they should be split out into separate API endpoints / actions. It grew this way organically, but its less than ideal, and we've run into a lot of permissions issues now that seem arbitrary.