You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the general consensus is that index refers to an Integer. This is clearly not a functionality bug in any way.
Moreover, we did mentioned in our UG that we should interpret index as a positive integer.
If anything, this seems to be the case of user expectation, where the user thinks that being able to input in a number that has a decimal point will work.
It would not make sense in any way to show the route at index 1.0 as an example.
What if we were to show the route at index 1.1 instead? That would not make sense at all.
It would be a functionality bug if we instead allowed decimals like "1.0", because it will be questionable to allow the user to input such values and have the command actually work.
You are clearly trying to break the program and it didn't break. How is this even a bug?
ಠ_ಠ
Changed this to severity.Low as it is a nonsensical issue. It does not even affect anything in the application.
A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
I typed this :
routeList 1.0
[original: nusCS2113-AY1920S1/pe-interim#1620]
The text was updated successfully, but these errors were encountered: