chiptopher / scalio Goto Github PK

Feature Request

When a login fails, pop up an error message saying that it failed.

Optional user story format:

Context

It's hard to know if the request is just lagging or if the request has failed when attempting to log in.

Acceptance Criteria

When the login fails, a box should pop up above the login button saying

Login failed. Please try again.

Feature Request

A text field that takes in a number of days, and then shows the weight change over that span of time.

Optional user story format:

Context

Sometimes a user will want to know how they've been doing over time. This is a more lightweight solutions than trying to get a graph to display.

Acceptance Criteria

When a user can enter the time span they'd like to know and have it display data.

Bug report

Since the Travis script isn't deploying anymore, there's no reason to do the build-prod portion with the frontend.

Feature Request

As a user, I would like to be able to add ingredients to a list of ingredients.

Acceptance Criteria

When I can click a button and fill out fields corresponding to different sections of the nutrition facts label.

Notes

Maybe have a fixed number of fields to start with, or allow users to add their own fields in their settings. The first one would be simpler now, but harder to work with in the future. Going with the second one now would prevent the need for a migration in the database later.

Feature Request

When a registration fails, pop up an error message saying that it failed.

Optional user story format:

Context

It's hard to know if the request is just lagging or if the request has failed when attempting to register.

Acceptance Criteria

When the registration fails because the account is already claimed, a box should pop up above the register button saying:

Account already claimed.

When the registration fails for any other reason, a box should pop up above the registration button that says:

Registration failed. Please try again.

Feature Request

The weight in the list should all be to the first decimal.

Optional user story format:

Context

Below you see the inputs 222.1, 222, and 244.121.

Acceptance Criteria

It should look something like this:

222.1   10-3-2018
222.0   10-3-2018
244.1   10-3-2018

Feature Request

Make it so that the weigh ins on the dashboard are shaded darker when they're included in calculating the rolling average.

Optional user story format:

Context

Since the rolling average is calculated as an average of all weigh ins in the last X number of hours, depending on when you view it there could be more than expected.

For example, imagine you have your average set to three days. If you put a weigh in late on Monday, it may still be included in the average calculation if you check early Thursday morning.

Acceptance Criteria

The last X number of hours worth of weigh ins are shaded darker.

Feature Request

Make it so that the delta weight over time is rounded to the second decimal.

Optional user story format:

Context

For data that has repeating decimals, the screen can get covered by a really long string.

Acceptance Criteria

Data is rounded to the second decimal.

Feature Request

Add the ability for scalio to be used as progressive web app.

Optional user story format:

Context

Opening chrome and then navigating to the page is a pain, and I'd like to just click a button on my home screen.

Acceptance Criteria

I can click a button on my home screen to get to the app.

Bug report

Sometimes when trying to connect, the website just falls over.

Actual behavior?

When trying to login, the login will be successful (in that, it won't show a login error), but won't actually log in.

Expected behavior?

It should log you in without error.

Feature Request

As a user, I would like the ability to create recipes that consist of a list of ingredients and the count of servings of that ingredient.

Related to #14 .

Optional user story format:

Context

Part of a list of features allowing users to keep track of their intake.

Acceptance Criteria

When I can select ingredients, associate servings with those weights, and save it as a recipe.

Bug report

The weight averages don't seem to be calculated correctly. Even if my rolling average is 3 days, it doesn't appear if the 231 is being included in the calculation at all:

Actual behavior?

Incorrect calculation of weight average.

Expected behavior?

Correct calculation of behavior. Assuming that it doesn't count the entry on the 20th because of timing, the average should be at 229.8. If it did include 232.2, then it would be even higher.