dorthu / economizerweb Goto Github PK

Automatically navigate when adding gas stop, but also navigate to/from add gas stop without other action

Right now, input fields go through very basic, if any, validation before passing values to the webservice. This should be improved.

While the reset password screen appears when loading the app with an active session, the redirect never happens on login - if visiting the app and logging in because you didn't have a session, no password reset is requested. This is compounded by issue #8, preventing password reset from appearing during normal use on mobile.

MPG doesn't normally vary a lot, so small changes look big over the y-axis. Display a fixed range from like 10 to 50, with some smarts for edge cases, so that small changes appear as they are: small.

The addGasStop endpoint accepts a double as total price paid - the client should do validation on input fields and strip extra characters, most notably the $ users may place in front of the price. Currently, if a $ is included in the price input, the server experiences an internal error and the client displays "Unable to Connect"

When the page is first loaded, if a cookie is found, it should renew the session. Error responses that indicate no/expired session should be handled properly.

I've heard some people talking about using Google Analytics or a similar tool in their own personal projects...maybe we should incorporate it here? Let's do some research, and implement if it looks like it could offer anything valuable.

Certificate chain not correctly bundled; Google Chrome on Android reports the site is not secure because of this.

Shows a graph of fuel economy over time, and has proper navigation to the other screens

Right now these all use http, but the prod endpoints had aught to be switched to https as soon as they deployment has a certificate and is configured correctly for it.

After leaving the page idle for a while, no longer able to send successful Ajax requests. Refreshing page fixes issue. Confirmed on Firefox for Android.

type="number" doesn't do the trick because FF Mobile fails to validate a decimal number as a number.

During the alpha release, it would be nice to display known issues on the site to allow users to work around them. This should query github for issues on either of the two repositories labeled "bug" and give a notice and explanation of them on the website.

The Known Issues sidebar only displays occasionally when pressing the Issues button - requires 3-5 presses in my testing (Repo'd on Firefox for Android)

My session expires between visits, requiring a new login every time. Repo'd on Firefox for Android.