annikacodes / betterpoll Goto Github PK

May be just a dev-environment phenomenon, so I should investigate it after deployment.

Maybe allow opt-in to searching by description/title in the future. Not sure how the DB would take this.

It's probably best to add a configuration property with allowed origins? Regardless, accepting all should only be done in testing.

Maybe better to implement at the hosting level?

Let users see who is winning before the poll ends! Have a setting to restrict to users who've already voted if IPs are being recorded.

Also, add an endpoint check if the user's IP has already voted in the poll (& redirect to the visualization if they have).

/poll/<id> if the poll is open

Query the API for # of polls active/total, whether it's active, etc.

This will stop CI failures while preserving testability/

It's not super useful + the code could be cleaner (one backend/ dir). Expand the regular unit tests maybe.