phildenhoff / choretracker Goto Github PK

I'd like a live demo hosted at denhoff.ca/choretracker. It'll have to be run through Firebase as that's how denhoff.ca is hosted.

Not having a tasks.csv should be a cause for alarm - but a default should be created.

Not having a scoreData.txt should not be an issue.

Do you want to request a feature or report a bug?
Bug

What is the current behaviour?
The red log out bar can cover "Nevermind, take me home" on some screens (and for the most part)

If the current behaviour is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via gif/screenshot along with a full stack trace
Literally mouseover the logout area, you'll see what I mean.

What is the expected behaviour?
Logging out shouldn't block that element. Also, discoverability is almost 0 with the red log out bar fully disappearing.

New suggestion: keep a 1 - 10px line at the bottom of the screen to remind the user where the log out function is.

Current behavior
The site is hardcoded to shift the first element of the confirmation queue, but a user might want to confirm someone else's job even if theres is first. Obviously a user cannot confirm their own tasks.

Expected behavior
Best explained as a scenario:
There are no chores in queue. I add a chore. Someone else adds a chore they did, but does not confirm mine. I go to confirm their chore. I am told "There are no chores available to confirm", because item 0 in the queue is my chore.

I should be able to confirm that second users chore.

Claims should have a uuid for clarity, especially in the confirmation stage.

At the moment the console on the browser errors out because you can't get element 5 of null. Need to provide a default text when there are no queue items.

Current behaviour
Confirmation queue uses awkward English to ask if a user did a task.

Expected behaviour
User experience should not be interrupted. Questions could be posed as "Did Phil fight a bear?" or "Is it true that Phil fought a bear?" Most likely is that verbs should be unconjugated (Woo, language!).

I know. Oh god.

But the steps are small, and easy:

• Break styling into multiple parts if need be
• Create state with current page domain
• Props should have task data in it, other things
• Do magic

The benefits of this are:

1. Reduced web socket data transfer. ATM a socket authorises the user on each load, sends all the score data, refreshes the high-score, and possibly more. By turning the site into a one-page React app, the overhead won't be required.

2. Improved styling & page creation. Making hindsight changes to old webpages will be significantly easier when they are broken down into specific parts that do specific things.

3. It'll fix those "resource not found" pages that keep occurring, by default.

4. It's good practice for work. That's pretty self-explanatory.

Current behavior
Log-in is accomplished by trusting that the user isn't lying.

Preferred behavior
Log-in should be secure, with either unencrypted passwords (bad) or using Auth0 /alternative authorisation means (better).

Sent from my OnePlus ONEPLUS A5000 using FastHub

Do you want to request a feature or report a bug?
Bug

What is the current behaviour?
"Thank them" is not aligned with the slider on the confirm page.

If the current behaviour is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via gif/screenshot along with a full stack trace

What is the expected behaviour?
Should be vertically aligned in the center compared to the slider.