having an integer in `EXERCISE_NAME` produces unnecessary warning message
Opened this issue · 1 comments
If I add a workout name that consists of numbers (e.g. press8times
) it would consider the portion with the number onwards to be the WEIGHT_USED_WEIGHT_UNIT
input when it should not still be EXERCISE_NAME
input.
Similarly, if I have 8kg
or 8lb
within my description, it would consider it to be WEIGHT_USED_WEIGHT_UNIT
input when it should still be part of EXERCISE_NAME
input.
It does not seem to specify in the UG or DG that strings without integers can only be used in EXERCISE_NAME.
Similarly, if a number is used for the FOOD_NAME
for /cadd
command, it would read it as the CALORIES
instead and produce a warning message.
Team's Response
Exercise names do not have numbers in them but agree that a few food items have numbers in their names and should be addressed
Items for the Tester to Verify
❓ Issue severity
Team chose [severity.Low
]
Originally [severity.Medium
]
- I disagree
Reason for disagreement: [replace this with your explanation]