chouette-core/spec/services, branch 6979-ruby-controls-sets Chouette manage transport static data Update RouteWayCostCalculator spec. Refs #6884 2018-05-17T08:14:36+00:00 Alban Peignier 2018-05-17T08:14:36+00:00 d1963bdd52c1d0fdc23606cd21e79b1f4fc9dc82 






Update RouteWayCostCalculator spec after Faraday. Refs #7032
2018-05-16T15:00:48+00:00

Alban Peignier

2018-05-16T15:00:41+00:00

70d55a1a62a2207453b738cb81003f57c537473c












Merge pull request #553 from af83/6884-tomtom-matrix--handle-error-when-response-doesn,t-inclu
2018-05-16T13:42:24+00:00

Alban Peignier

2018-05-16T13:42:24+00:00

223d988ef59e562b201cac8391c397630c8953e5

Handle API error(s) in Tomtom matrix. Fixes #6884




Handle API error(s) in Tomtom matrix. Fixes #6884






Define a dummy TomTom api_key in spec
2018-05-13T09:21:12+00:00

Alban Peignier

2018-05-13T09:21:12+00:00

458f55a73105d8ade30f9874e8ca6b82e86011f1












Fixes RouteWayCostCalculator spec. Refs #6661
2018-05-04T08:52:44+00:00

Alban Peignier

2018-05-04T08:52:44+00:00

172cf6b13923c97af19ebe602c0a628ee8e2f0ab












RouteWayCostCalculator: Don't update `costs` if response errors
2018-05-02T17:27:39+00:00

Teddy Wing

2018-05-02T17:27:39+00:00

d53978539c71d598d7cb5f47ad9e3f30a83eb06a

If there's an API error, we shouldn't update the route's `costs` field.
Let's say we've already calculated some costs for a route A. We then edit
and re-save A, which triggers a recalculation of the costs. Now the
TomTom API responds with an error. We don't want to overwrite our
existing costs with an empty array because they could still be useful.
In this case, we should instead keep the existing costs we already had.

To achieve this, move the `RemoteError` rescue into
`RouteWayCostCalculator`, leaving the error unhandled in
`TomTom.matrix`.

Refs #6884





If there's an API error, we shouldn't update the route's `costs` field.
Let's say we've already calculated some costs for a route A. We then edit
and re-save A, which triggers a recalculation of the costs. Now the
TomTom API responds with an error. We don't want to overwrite our
existing costs with an empty array because they could still be useful.
In this case, we should instead keep the existing costs we already had.

To achieve this, move the `RemoteError` rescue into
`RouteWayCostCalculator`, leaving the error unhandled in
`TomTom.matrix`.

Refs #6884







Refs #6360; Add checks on calendars during WorkbenchImport
2018-04-09T09:22:40+00:00

Zog

2018-04-09T09:20:56+00:00

27442a9ffe40d0f548b1dc99ab917a8d8b0a02a2












RouteWayCostCalculator: Use `TomTom.matrix` instead of batch
2018-03-27T14:46:18+00:00

Teddy Wing

2018-03-27T09:18:17+00:00

f257a8b3a7ae4c59c6907b41f6e8d7dc74259917

Calculate routes using the TomTom matrix API. Update the spec's HTTP
request stub accordingly (note that the stub is still fake).

Refs #6222





Calculate routes using the TomTom matrix API. Update the spec's HTTP
request stub accordingly (note that the stub is still fake).

Refs #6222







Route: Add `#calculate_costs!` to populate `#costs` with `WayCost`s
2018-03-14T15:42:02+00:00

Teddy Wing

2018-03-13T14:37:55+00:00

dbcd099b3d38f7c584450edffc8bee0a2502b170

This new method will launch a worker that takes the route's `StopArea`s,
converts them to `WayCost`s, sends them to the TomTom API to calculate
distance and time costs, and saves those costs to the route's `costs`
field.

Refs #6095





This new method will launch a worker that takes the route's `StopArea`s,
converts them to `WayCost`s, sends them to the TomTom API to calculate
distance and time costs, and saves those costs to the route's `costs`
field.

Refs #6095







Refs #6133; Fix specs
2018-03-12T11:00:15+00:00

Zog

2018-03-09T16:25:38+00:00

3a738f4509a67d5024fb85bb551c7ec285cd031e