Part 3, Comments App: Admin and Reply
This is a continuation of an earlier post, see:
- Part 1, Comments App: Overview
- Part 2, Comments App: Proof of Work
- Part 4, Comments App: Integration
- Test the Comments App
I try to summarize the general thoughts of the new features; replies and the administrator interface. Let me know in the comments down below, if more details are desired.
Being able to comment on posts is nice, but getting / giving a reply if there was a question or a need to add something is simply a must. So the first feature I wanted to add is a reply function. At first, I considered allowing anyone to reply to anyone, but in this particular app, where no login is needed to write comments, just some security measures, it will get messy quickly… That’s why I decided to only allow the blogger / admin to reply. This should hopefully cover about 90% of the use cases…
The reply is directly bound to a comment’s id. And should also be editable.
As a result of the mentioned “admin only reply feature” above, an administrator interface is crucial. But how and with what technology? I quickly knew, that I would be the fastest with the lightweight js-framework vue, with which I was already familiar to a certain degree.
- See what blog posts have comments, and how many.
- Detail view comments
- Possibility to reply
- Delete comments
- A overview of the latest comments or highlighted sub-chapters, where new comments appeared.
I took the newest version of Vue31. I already knew Vue2 and worked with its options API, which you still can with Vue2. But in this application, I decided to only use the new composition API, which promises; better performance and a much better coding experience, because you don’t have scattered code over the options in your file and it should be easier to produce reusable components.
The css part I made as easy and minimal as possible and wrote / edited it myself. Vue also comes with nice development features like a webserver with live reloading capabilities and a lot more, which, even with such a simple goal, is worth it!
In the backend I added a new controller, which only allows authenticated access. At the moment one can set one admin / blogger user. The implementation is a simple in memory user, who can be set with environment variables (see docker-compose in project root).
environment: ... SPRING_SECURITY_USER_NAME: user SPRING_SECURITY_USER_PASSWORD: PleaseChangeMe
I won’t go into detail about the new API-Calls, because it isn’t necessary to understand them for the integration of comments. If future contributors feel the need for further documentation, I will add something.