avoid making this the default config as test use it too

README.md

@@ -23,6 +23,7 @@ There is [an experimental `navi` branch](https://github.com/graphhopper/graphhop
  * Fork the repository and create a pull request. Contributions are welcome. Feel free to discuss your changes in our
    [forum](https://discuss.graphhopper.com/) or the GitHub [issues](https://github.com/graphhopper/graphhopper-maps/issues).
  * You can build the production bundle using `npm run build`.
+ * If you use the Directions API edit the config to show profile icons properly (see 'Advanced configuration' section below).
 
 ## Help with translations:
 

config.js

@@ -37,13 +37,13 @@ const config = {
     // Use 'profiles' to define which profiles are visible and how. Useful if the /info endpoint contains too many or too "ugly" profile
     // names or in the wrong order. The key of each profile will be used as name and the given fields will overwrite the fields of the
     // default routing request. The following example is tuned towards the GraphHopper Directions API. If you have an own server you might want to adapt it.
-
-    profiles: {
-        car:{}, small_truck:{}, truck:{}, scooter:{},
-        foot:{ details: ['foot_network'] }, hike:{ details: ['foot_network'] },
-        bike:{ details: ['get_off_bike', 'bike_network'] }, mtb:{ details: ['get_off_bike', 'bike_network'] }, racingbike:{ details: ['get_off_bike', 'bike_network'] },
-    }
-
+    //
+    // profiles: {
+    //    car:{}, small_truck:{}, truck:{}, scooter:{},
+    //    foot:{ details: ['foot_network'] }, hike:{ details: ['foot_network'] },
+    //    bike:{ details: ['get_off_bike', 'bike_network'] }, mtb:{ details: ['get_off_bike', 'bike_network'] }, racingbike:{ details: ['get_off_bike', 'bike_network'] },
+    // }
+    //
     // E.g. the 'bike' entry will add a "bike" profile for which we send a request with the specified 'details' parameter. You can even change the profile itself when you specify
     // bike: { profile: 'raw_bike', ... }
 }