Feature: query auto-prediction

[JasonBarahan]

Right now the program's accepted inputs are too specific. For example:

• GO stations must have the "GO" suffix attached (for example, searching "Milton" yields an error, but searching "Milton GO" yields the desired effect
• Stations with unusually long names must be typed in exact case ("Durham College Oshawa GO" must be typed; "Oshawa GO" or "Oshawa" do not work)
• Input is case-sensitive

Solutions:

• Create 'search shortcuts' for stations (e.g.: searching 'Milton' yields results for 'Milton GO')
  • This would require creating an automatic search predicton engine/algorithm.
• Compare the input names to the names in stopData using lowercase

[JasonBarahan]

Due to time constraints and reduction in project scope, we've changed it so that station names (including suffixes) must be typed in with proper casing.

Linking short-form searches to GO stations (akin to a query autofill/prediction tool) would require additional time to implement AND would count as an additional feature.

Note

Title has been changed:

Bug: Scope of accepted inputs is too narrow

to

Feature: query auto-prediction