chouette-core/spec/models, branch 6642-fix-metadata-serialization Chouette manage transport static data Fixes JourneyPattern specs (by adding position in JourneyPattern state). Refs #6193 2018-04-22T15:46:50+00:00 Alban Peignier 2018-04-22T15:46:50+00:00 8eacb2238bb70f774f89d4cad4311725d826b2a0 






Fixes JourneyPattern specs with distance is not defined/zero. Refs #6413
2018-04-22T15:34:15+00:00

Alban Peignier

2018-04-22T15:34:15+00:00

ed97c41fcb9d3cd2ba16c77c0ec166500803752f












Fixes Calendar::Period specs. Refs #5519
2018-04-22T14:55:49+00:00

Alban Peignier

2018-04-22T14:55:49+00:00

fdd91bf918c9aaf35d8381c553652458c850b609












Refs #5519; Authorize 1-day calendars
2018-04-20T05:05:31+00:00

Zog

2018-04-19T12:30:06+00:00

ad9e5c93133bf38eec1a9a2c533e783846936de8












Merge pull request #488 from af83/6477-use-custom-fields-in-checksums
2018-04-19T21:42:20+00:00

Alban Peignier

2018-04-19T21:42:20+00:00

66257b30c12197d24018f234e73aa1da0631f04d

Use custom fields values in checksum calculation. Refs #6477 




Use custom fields values in checksum calculation. Refs #6477 






Merge pull request #487 from af83/6410-route--don,t-run-calculate_costs-during-referential-mer
2018-04-18T20:56:28+00:00

Alban Peignier

2018-04-18T20:56:28+00:00

15a389600730c5e6c393a5537f9c646d1d28a134

Route: Don't run `#calculate_costs!` during a referential merge. Fixes #6410




Route: Don't run `#calculate_costs!` during a referential merge. Fixes #6410






Manage download uri in Import::Gtfs (with or without schema or port). Refs #6368
2018-04-18T19:49:18+00:00

Alban Peignier

2018-04-18T19:46:11+00:00

35ef1a2abe0a664b259c99538bb95f04ef6408d4












Refs #6477; Use custom fields values in checksum calculation
2018-04-16T17:49:54+00:00

Zog

2018-04-16T17:49:54+00:00

34cf69c9cdebe5846426e6c69ab919d9c5a640a4












Route: Don't run `#calculate_costs!` during a referential merge
2018-04-16T15:46:36+00:00

Teddy Wing

2018-04-16T15:41:09+00:00

220e839fddec44c9a1e73fb5e7cd7f701faf726d

This callback got triggered during a referential merge, but it isn't
needed at that point. It should only be executed as a result of a user
updating the route (via the web interface).

Using Alban's suggestion, we can detect that we're in the process of a
merge if the associated referential is in a `ReferentialSuite`. Use this
as a condition to run the callback.

Refs #6410





This callback got triggered during a referential merge, but it isn't
needed at that point. It should only be executed as a result of a user
updating the route (via the web interface).

Using Alban's suggestion, we can detect that we're in the process of a
merge if the associated referential is in a `ReferentialSuite`. Use this
as a condition to run the callback.

Refs #6410







Refs #6179; Update acts_as_list
2018-04-16T12:49:15+00:00

Zog

2018-04-16T12:49:15+00:00

eb27950dcf348784dfd0519a92181e11a5c29645

And (hopefully) fix bugs on routes having duplicated positions





And (hopefully) fix bugs on routes having duplicated positions