chouette-core/app/controllers/concerns, branch 5505-custom_fields Chouette manage transport static data Refs #5349 @1h; Deactivate StopAreas instead of destroying them 2017-12-21T20:35:02+00:00 Zog 2017-12-20T16:48:17+00:00 e8285678efc9a62115fe0af4086c7a3959666bf8 - Update decorators (had to split `action_links` because of `StopPointDecorator` inheriting from `StopAreaDecorator`) - Add methods on model - Add routes - Add actions on controller (`Activatable` concern, shared with `LinesController`) - Add I18n keys 
- Update decorators (had to split `action_links` because of
`StopPointDecorator` inheriting from `StopAreaDecorator`)
- Add methods on model
- Add routes
- Add actions on controller (`Activatable` concern, shared with
`LinesController`)
- Add I18n keys
Improve styles in FeatureCheck code. Refs #5339 2017-12-20T20:06:41+00:00 Alban Peignier 2017-12-20T20:06:41+00:00 3305dca57e2e0a46b583f183040a82819ffd6efb 






Create Organisation#features and FeatureChecker controller concerns. Refs #5339
2017-12-20T16:23:47+00:00

Alban Peignier

2017-12-19T18:42:52+00:00

f31a79c5bc3678949b7334486daa196a17a5db92












Add has_paper_trail on models
2017-11-28T11:21:33+00:00

Xinhui

2017-11-22T15:32:32+00:00

86fd42a9136cb6eef87ecec3d0b2bcf579667798












Remove breadcrumb_controller
2017-10-26T09:51:07+00:00

Xinhui

2017-10-26T09:51:07+00:00

68bc446c975ff07cf2b4eb9f695da2dce93ee63d












Remove cattr_accessor form ransack date filter concern
2017-10-04T21:23:00+00:00

cedricnjanga

2017-10-04T21:22:45+00:00

92f6e7aa1427d7057f33db56a9c9434525901f11












RansackDateFilter: Move `end` statement and jiggle indentation
2017-10-03T16:05:52+00:00

Teddy Wing

2017-10-03T15:39:54+00:00

fdd6f25fbda4fa2c1f307248cddd316db88d2771

An `end` statement was missing to close off the `set_date_time_params`
method. Wondering if this is what was causing these test failures on the
build server:

    1) ComplianceCheckSetsController GET index should be successful
       Failure/Error: scope = self.ransack_period_range(scope: @compliance_check_sets, error_message: t('compliance_check_sets.filters.error_period_filter'), query: :where_created_at_between)

       NoMethodError:
         undefined method `ransack_period_range' for #<ComplianceCheckSetsController:0x0000000fa67e58>
       # ./app/controllers/compliance_check_sets_controller.rb:11:in `block in index'
       # ./app/controllers/compliance_check_sets_controller.rb:10:in `index'
       # ./spec/controllers/compliance_check_sets_controller_spec.rb:17:in `block (3 levels) in <top (required)>'

    2) Workbenches permissions on show view if present →  shows the corresponding button
       Failure/Error: scope = self.ransack_period_range(scope: scope, error_message:  t('referentials.errors.validity_period'), query: :in_periode)

       NoMethodError:
         undefined method `ransack_period_range' for #<WorkbenchesController:0x00000006cb4368>
       # ./app/controllers/workbenches_controller.rb:15:in `show'
       # ./spec/features/workbenches_permissions_spec.rb:15:in `block (3 levels) in <top (required)>'

Worth a try.





An `end` statement was missing to close off the `set_date_time_params`
method. Wondering if this is what was causing these test failures on the
build server:

    1) ComplianceCheckSetsController GET index should be successful
       Failure/Error: scope = self.ransack_period_range(scope: @compliance_check_sets, error_message: t('compliance_check_sets.filters.error_period_filter'), query: :where_created_at_between)

       NoMethodError:
         undefined method `ransack_period_range' for #<ComplianceCheckSetsController:0x0000000fa67e58>
       # ./app/controllers/compliance_check_sets_controller.rb:11:in `block in index'
       # ./app/controllers/compliance_check_sets_controller.rb:10:in `index'
       # ./spec/controllers/compliance_check_sets_controller_spec.rb:17:in `block (3 levels) in <top (required)>'

    2) Workbenches permissions on show view if present →  shows the corresponding button
       Failure/Error: scope = self.ransack_period_range(scope: scope, error_message:  t('referentials.errors.validity_period'), query: :in_periode)

       NoMethodError:
         undefined method `ransack_period_range' for #<WorkbenchesController:0x00000006cb4368>
       # ./app/controllers/workbenches_controller.rb:15:in `show'
       # ./spec/features/workbenches_permissions_spec.rb:15:in `block (3 levels) in <top (required)>'

Worth a try.







Refs #4665
2017-10-03T14:33:49+00:00

cedricnjanga

2017-10-03T13:32:26+00:00

9ea95b98c52f99494a13befa54cfd8cd298ab0c4

Adapt date filters helpers according to this new concern
Try to correct build error : "ransack period range undefined"

All tests pass on my machine

Refs #4661
Remove string column from ComplianceCheckSet





Adapt date filters helpers according to this new concern
Try to correct build error : "ransack period range undefined"

All tests pass on my machine

Refs #4661
Remove string column from ComplianceCheckSet







Refs 4665 Update time_table for to adapt to ransack date filter concern
2017-10-03T13:09:20+00:00

cedricnjanga

2017-10-03T12:26:59+00:00

7775030c3f84e0673bbf68e7a60a3ed4798f6b91












Refs #4665
2017-10-02T15:36:41+00:00

cedricnjanga

2017-10-02T15:34:49+00:00

cba31dc411ceb47f80202c1d3a32a2e031630b13

Add a controller concern to deal with date filters





Add a controller concern to deal with date filters