| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-03-26 | Refs #6218; Limit accessible exports for workgroups | Zog | |
| 2018-03-18 | Refs #6210 Remove status value attribue from Chouette::VehicleJourney and ↵6210-remove-attributes-from-models | cedricnjanga | |
| section status fron Chouette::JourneyPattern | |||
| 2018-03-15 | Merge pull request #379 from ↵ | Alban Peignier | |
| af83/6095-route--calculate-distance-and-time-cost-between-stops Calculate distance and time cost between Route stops. Refs #6095 | |||
| 2018-03-15 | Refs #6033 Update all StopArea#confirmed_at | cedricnjanga | |
| 2018-03-15 | Refs #6033 Add confirmed_at attribute to Chouette::StopArea | cedricnjanga | |
| 2018-03-14 | Add `costs` column to `Chouette::Route` | Teddy Wing | |
| This allows us to store `WayCost`s for a route so we can use those values as pre-filled defaults for a `JourneyPattern`'s costs. Refs #6095 | |||
| 2018-03-14 | Refs #5972 @1h; Automatic registration_number generation | Zog | |
| 2018-03-12 | Fix migration 20180306152953_update_imports_names with compact Refs #6133 @1 | Luc Donnet | |
| 2018-03-12 | Refs #6133; Add options on the Exports, and forward them tu the UX | Zog | |
| 2018-03-12 | Refs #6133; Exports naive implementation | Zog | |
| 2018-03-12 | Refs #6133; Fix specs | Zog | |
| 2018-03-12 | Refs #6133; Remove former implementation | Zog | |
| 2018-03-05 | Merge pull request #359 from af83/6068-simple-exporter | Alban Peignier | |
| Simple exporter. Refs #6068 | |||
| 2018-03-02 | Refs Refs #3562 Add workbench CCSET affectation | cedricnjanga | |
| 2018-03-02 | Refs #6068; Create a SimpleExporter model | Zog | |
| This is an STI model, inheriting from SimpleInterface SimpleImporter has been updated to work likewise | |||
| 2018-02-27 | refs #5878; Remove hard link between a ComplianceCheck and the associated ↵ | Zog | |
| ComplianceControl | |||
| 2018-02-20 | Refs #5765 @6h; Add a customizable importer mechanism | Zog | |
| 2018-02-07 | Set all existing `StopArea`s with nil `kind`s to `:commercial` | Teddy Wing | |
| The other migration for this in `db/migrate/20180126134944_add_kind_to_stop_areas.rb` didn't handle `kind IS NULL`. Since all the `kind`s were initialised to NULL when the column was created, the `where` query didn't select any stop areas because it was looking for those with some varchar value, and thus it wasn't able to update any. This ensures our existing records all have a `kind` in case we end up using the field in a template at some point and our old data bugs out. Refs #5817 | |||
| 2018-02-06 | Refs #5758 @1h; Add localized names to StopAreas | Zog | |
| 2018-02-06 | Refs #5682 @3h; Use same UI as for timetables | Zog | |
| 2018-02-06 | Refs #5682; Set default value for application days | Zog | |
| 2018-02-06 | Refs #5682; Add application_days field to calendars | Zog | |
| 2018-02-06 | Refs #5750; Fix validation | Zog | |
| 2018-02-06 | Refs #5750 @1h; Manage non-commercial StopAreas | Zog | |
| - Add a `kind` attribute - Hide irrelevant fields in the form | |||
| 2018-02-06 | Refs #5750 @1h; Add a "kind" attribute to StopAreas | Zog | |
| This determines if the StopArea is commercial or not The useless fields are hidden in the form for the non-commercials ones | |||
| 2018-01-23 | First draft for including calendars into workgroup for having appropriate ↵ | cedricnjanga | |
| scoping | |||
| 2018-01-11 | Add Referential#merged_at and make Referentials archived and merged. Refs #5559 | Alban Peignier | |
| 2018-01-10 | Use jsonb and default to create vehicle_journeys#custom_field_values. Refs #55055505-custom_fields_with_jsonb | Alban Peignier | |
| 2018-01-10 | Fixes: #5505@0.25h; Invesitgating the failure to compute a distinct join on ↵ | Robert | |
| vehicle_journeys Solution: custom_field_values: json -> jsonb | |||
| 2018-01-10 | Fixes: #5505@2h; Migrations, specs and implementations | Robert | |
| - Migration index_resource_type_on_custom_fields - Specing behavior of custom field's resource (VehicleJourney) - Migration create json col custom_field_values for resource (VehicleJourney) - Create accessor methods inside resource (VehicleJourney) | |||
| 2018-01-10 | Refs: #5505@1h; Spec discussed, model scaffolded [amend me] [skip-ci] | Robert | |
| 2018-01-10 | Fixes: #5499; Added validations and associations | Robert | |
| 2018-01-10 | bup [amend me] [skip-ci] | Robert | |
| 2018-01-10 | Refs: #5499@0.5h; fixed migration (ids type of rails generator is not conform) | Robert | |
| 2018-01-10 | Refs: #5499@0.5h; Scaffolded Workgroup | Robert | |
| Next: - spec associations and name - spec initialisation - implement | |||
| 2018-01-08 | Refs #5455 @6h; Add time and distance between stops in Journey Patterns | Zog | |
| - Adds a `JSON` attribute in the model - Adds the fields in the editor | |||
| 2018-01-05 | Create Merge operation. Refs #5299 | Alban Peignier | |
| 2017-12-27 | Refs #5407; Fix CI | Zog | |
| 2017-12-27 | Refs #5407; | Zog | |
| :fire: useless code Rename some vars | |||
| 2017-12-27 | Refs #5407; Fix CI | Zog | |
| 2017-12-27 | Refs #5407 @2h; Model implementation | Zog | |
| - Link PurchaseWindows to VehicleJourneys in the model - Add an autocompletion endpoint | |||
| 2017-12-21 | Merge branch 'master' into ↵ | Luc Donnet | |
| 5316-migrate-compliance-control-and-check-attributes-from-hs | |||
| 2017-12-21 | Add `down` to 20171218174509 Hstore to JSON migration | Teddy Wing | |
| Copy Cédric's JSON to Hstore migration for the `down` here to give us the ability to roll back. I'm guessing the solution probably comes from here: https://stackoverflow.com/questions/28315948/casting-json-to-hstore-in-postgres-9-3/28319295#28319295 Refs #5316 | |||
| 2017-12-21 | Change `compliance_{controls,checks}` `control_attributes` to JSON | Teddy Wing | |
| Make these columns JSON fields again. Do this because of bugs trying to validate types with `hstore_accessor` (https://github.com/devmynd/hstore_accessor/issues/78). With a JSON field, types are preserved and we don't have to deal with casting back and forth. Previously we had converted to Hstore because the Java IEV application used an older ORM version (maybe Hibernate) that didn't support the Postgres JSON type. Because of the validation problems with Hstore, the Java application has been updated to support JSON fields. Thanks to this Stack Overflow post from 'a_horse_with_no_name' that describes how to convert from Hstore to JSON types in Postgres: https://stackoverflow.com/questions/33732529/postgres-how-to-convert-hstore-to-json-datatypes#comment55234342_33732529 Converting in this direction seems to me to be much safer because we're not losing type information. All the values should be hashes of strings, which should convert without issue into JSON. Refs #5316 | |||
| 2017-12-21 | Merge pull request #150 from af83/5301-add_business_calendars | Luc Donnet | |
| Refs #5301 First draft for Business Calendars | |||
| 2017-12-21 | BusinessCalendar => PurchaseWindow | cedricnjanga | |
| belongs_to referential | |||
| 2017-12-21 | Fix migrations, locales, view and exclude calendar timetable in concern Refs ↵ | Luc Donnet | |
| #5301 | |||
| 2017-12-21 | Refs #5301 First draft for Business Calendars | cedricnjanga | |
| 2017-12-20 | Add StopArea#waiting_time with support in stop_areas#index/show. Refs #5351 | Alban Peignier | |
| 2017-12-20 | Create Organisation#features and FeatureChecker controller concerns. Refs #5339 | Alban Peignier | |
