From cfc85d84ecbd89beada7191a6253e97a936d3405 Mon Sep 17 00:00:00 2001 From: Jaakko Malkki Date: Fri, 17 Aug 2018 15:19:35 +0300 Subject: [PATCH] More detailed description for 'maxWalkDistance' --- src/main/java/org/opentripplanner/index/IndexGraphQLSchema.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/org/opentripplanner/index/IndexGraphQLSchema.java b/src/main/java/org/opentripplanner/index/IndexGraphQLSchema.java index 83653eaa184..2923c5db8e7 100644 --- a/src/main/java/org/opentripplanner/index/IndexGraphQLSchema.java +++ b/src/main/java/org/opentripplanner/index/IndexGraphQLSchema.java @@ -574,7 +574,7 @@ public IndexGraphQLSchema(GraphIndex index) { .build()) .argument(GraphQLArgument.newArgument() .name("maxWalkDistance") - .description("The maximum distance (in meters) the user is willing to walk. Defaults to unlimited.") + .description("The maximum distance (in meters) the user is willing to walk per walking section. If the only transport mode allowed is `WALK`, then the value of this argument is ignored. \n Default: 2000m \n Maximum value: 15000m \n **Note:** If this argument has a relatively small value and only some transport modes are allowed (e.g. `WALK` and `RAIL`), it is possible to get an itinerary which has (useless) back and forth public transport legs to avoid walking too long distances.") .type(Scalars.GraphQLFloat) .build()) .argument(GraphQLArgument.newArgument()