Distance (km, mi) logging bugs

[ddakotac]

Hello! It seems like when logging distance decimal values cannot be input, returning an error "please enter a valid value. The two nearest valid values are 1 and 2" say when inputting 1.5 mi.

There are a few other bugs around the mileage I've noticed but that one is the most important as it pretty much makes that feature unusable.

A few other bugs I've noticed that are annoying but don't make it unusable:

• I've set up the exercise in my workout routine with Miles as the rep unit, and mph as the weight unit, yet each time I log I still have to manually change the units (still defaults to reps/lbs)
• Even when inputting as miles/mph, it often displays in logs as km instead. This looks like this only happens on the mobile app because it has a different menu for displaying logs

Steps to Reproduce

1. ... Either in the mobile app or on the website, log a workout exercise "run"
2. ... Change the reps to distance (miles or km) and enter a decimal value (eg 1.5)
3. ... Click "Save"

Expected results: That a decimal distance value would be saved to the program.

Actual results: "Please enter a valid value. The two nearest valid values are 1 and 2."

Minor bugs:

1. Defaults to reps/weight even when different units are chosen for that exercise
2. Results display as km even when mi is chosen, at least on the mobile app

Thanks for any help!

[rolandgeider]

oh, you are right! Changing the field from integer to float is gonna break a lot of things, mhhh. But not having it preselect the correct units should obviously not be like that