[jormun]: For departure_boards, group_by_destination is activable in config

[kadhikari]

• For client as lyon, rennes and others, group_by_destination is False by default (retro-compatibility). When only one route is displayed even if the line is splitted in two directions, group_by_destination should be deactived. Ex: https://playground.navitia.io/play.html?request=https%3A%2F%2Fapi-cus.navitia.io%2Fv1%2Fcoverage%2Ffr-se-lyon%2Flines%2Fline%253Atcl%253AC24%2Fstop_areas%2Fstop_area%253Atcl%253ASA%253A5765%2Fstop_schedules%3Fcount%3D50%26

• For client as ratp, destineo group_by_destination should be activated. At least one route par direction is displayed and hence date_times should be grouped by destination. Ex: http://playground.navitia.io/play.html?request=https%3A%2F%2Fapi-cus.navitia.io%2Fv1%2Fcoverage%2Ffr-pdl%2Fstop_points%2Fstop_point%253APDL%253AMOBIITI%253AQuay%253A82%2Flines%2Fline%253APDL%253ACAC%253ALine%253A1%253ALOC%2Fstop_schedules%3Fdata_freshness%3Dbase_schedule%26

• Tests are added to verify configuration.

[sonarcloud[bot]]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud