![Cover image for EasyPollVote [Dev Log #3]](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5gmol9xj68j07hif9oaz.png)
Welcome to the Third DEV LOG!
Welcome to the third Dev Log of my full stack application called EasyPollVote (EasyPV)!
Wh...
For further actions, you may consider blocking this person and/or reporting abuse
Haha come on folks, let's vote in my custom poll!!! easypollvote.vercel.app/poll/78
I prefer Umbreon, but I have to admit I like the name Sylveon 😂
How about Gengar @sylwia-lask ?
Umberon is dark-type, so it beats Gengar easily!
Ghost / Poison, madam. Poison attacks beat dark :D
Ah, damn! So it's a fair fight 🤣
The
actionfield as a switch-case router is the detail that caught my attention. It's the kind of pattern you reach for when you're building something real and the clean abstractions haven't arrived yet. You need one endpoint to handle multiple form types, you don't want to over-engineer it, so you toss anactionstring into the payload and let the backend sort it out. It works. It's readable. It'll probably get refactored later, and that's fine.What I think is worth flagging is that
action: "Demo"is currently client-side and hardcoded. The comment says it's not uploaded to the database, which makes sense—it's routing metadata, not user data. But if someone opens the browser dev tools and changes that"Demo"string to"Live"or"Admin"before submitting, does the backend just trust it? That's the kind of thing that's harmless in a university project but becomes a real vulnerability if the switch case ever includes privileged paths. Not a problem now. Just one of those things that quietly graduates from "works" to "wait, is this safe" once more people start using it.The
@bingkahumention got a laugh. There's always one person who stress-tests your database with joke votes during development, and honestly it's useful. Better to find edge cases from someone goofing around than from a real user who's confused. Did any of those many votes surface something you hadn't thought about, or was it just volume?Hey Thanks for the feedback!
Unfortunately, yes. There are currently no safeguards for that. As of now, it is not really a priority because the worst case scenario is uploading to the wrong database, hence resulting in an error due to a mismatch. In the future, if I were to do authentication, that is something to actually think about.
Pretty much both. I was hoping to see how it would look like in the back-end and how data will populate. To be fair, I mention to put fake information just in case. Sometime it is sometimes it's not. Either way, seems to be working as expected. Currently, there is no implementation where you can only vote once. I am planning on doing email verification where you enter your email and you get a 6 digit code to verify. Once you have voted, you cannot use that same email again.
Thanks again!
Bro,It would be great to add some simple validation to improve poll accuracy
Right now it seems anyone can submit multiple responses, which can easily introduce bias. A few lightweight improvements could make a big difference :)
Basic IP-based restriction (limit repeated votes)
Email or ownership verification (optional but helpful)
Simple device tracking (to reduce duplicate submissions)
Rate limiting (to prevent spam/bot voting)
Hey Kushal! Hope you are well. I am hoping for the "Email or ownership verification". I think it's a good step but I am holding that off for the summer time for now! Thanks :D
okie :)
This is why I started my project from scratch instead of
forking an existing codebase. The temptation to fork
Substrate or Tendermint was real but you inherit years of
decisions that don't match your use case. Starting clean
is slower but every line exists for a reason you
understand.
Great point! It's always a good idea to start from scratch. The only case for forking an existing project is if you are working to contribute to OpenSource and fixing a bug that you wanted to fix.
Thanks :D
I will try to use it next week andprovide you with feedback
wow this is sick!
Thanks Jack! :D
Tailwind or Standard?
easypollvote.vercel.app/poll/82
Cool I also work on an pokemon project, but with web3 and zk. My last project for frontend and smart-contracts.
Btw feel free to checkout my article, I mentioned you broskito.
Sounds good! and yes, I saw your latest article about mentioning me about the markdown. Thanks for the mention :)
Nice dev log update consistent iteration like this is how real products evolve. Small features + feedback loops usually matter more than big initial builds.
Thanks Laura!
Hi there! Have you considered separating each action into dedicated API routes instead of relying on a single endpoint with a switch-case? What trade-offs led you to this design?
Hey Sahl! There was an issue I came across (that I do not remember) that led me to create a single endpoint with switch-cases. I am planning on refactoring the code to make it more cleaner and also for security reasons I can imagine. It was built as I go type and there wasn't really a design to go out of. Thanks Sahl!
Such initiatives are important for bridging the gap between education and industry skills. Vctroid Concepts Pvt Ltd is doing a great job in preparing students for the future.