Comment API status

[avivace]

Aight, this wasn't as trivial as we expected, since a lot more factors appeared while implementing the basic routes.

I guess we need to do this the long way round: I propose to stop the development here and move to a separate module.

Priorities are:

• Basic view and edit routes (backend)
• Basic frontend rendering of the comment tree

We could then proceed to decide on stateful actions (backend side):

• How a delete action should be perfomed and how affects the parent comment and replies
• Voting system
• Comments tree handling

Does this makes sense to you, @dennib ?

[dennib]

As discussed yesterady I will continue the development on comment-api branch, we should be close to a basic functional version of "Comment System"

[dennib]

Update:

• 897c133 adds /add/ route for comment posting
• 4989cf0 /view/ method is now complete, it responds with comments and comments related info in form of JSON data, comments tree template is rendered completely on frontend now

Still missing correct visual behavior for the moment a comment has been added, I will continue there and then I'll focus on /edit/ route.

Every bit of comment system on "old" routes.js file should be useless now, I'll check and confirm (also removing those parts) later

[avivace]

Gotcha. Confirm that everything I removed on routes was just backend/sync rendering so we can go completely async with the API endpoints you mentioned

[dennib]

Ok I checked, I can confirm! Those parts are not needed anymore (or they are rewritten elsewhere). Comment System functionalities are now completely async with the use of API endopoints mentioned above (for which I still have to write the wiki documentation :P)

[dennib]

Update:

• 723dade adds last expected route: /edit/

I'm ready to merge :)

[avivace]

Nicely done. Go ahead.

Feel free to open a PR if you need help in solving merge conflicts.