Feature improvement:
- Selecting a route using start/end stops could be cumbersome as the selection allowed non-matching stops and one had to retry to get a proper pair. Now the code makes sure that the selected stop match by first selecting a start stop and then presenting a list of eligible end stops, see documentation HERE
- Selecting a route using start/end stops would only provide departures for today and, if selected, tomorrow ... and sometimes even none if nothing is offered for today/tomorrw. Now the entity will present the next departure(s) without date-limitation, only limited by the dates stored in the feed/db
Other:
- substantial code revision, removing edge cae issues, both in route-based as well as in local-stop configurations
- automated tests added and improved
Largely provided with the help of @Pulpyyyy