chouette-core/app/decorators, branch compliance_control Chouette manage transport static data ComplianceControlSet#show add compliance_control create link 2017-09-21T10:07:41+00:00 Xinhui 2017-09-21T10:07:41+00:00 f0516f1d23d8ebd9b4da328c86fcdaf6c5ee63a2 Refs #4563 
Refs #4563
Move ComplianceControl#index into ComplianceControlSet#show 2017-09-21T09:47:18+00:00 Xinhui 2017-09-21T09:47:18+00:00 9b87e5896921ac735393539d5bc3f41907f9e0ad Refs #4579 
Refs #4579
Compliance Control decorator 2017-09-19T12:49:14+00:00 Xinhui 2017-09-19T10:33:36+00:00 7110330a7e154fb8d746f6b15e12c7b42c6c00dc Refs #4543 
Refs #4543
create base structure for compliance_control_sets 2017-09-14T14:28:54+00:00 Guillaume 2017-09-14T14:28:54+00:00 1e58dfdbfbecccda78e2fe3854b2ba04a72bd511 






Apply object id changes to views
2017-09-13T13:39:50+00:00

cedricnjanga

2017-09-13T13:39:34+00:00

4804a4886c5267c1be1c367caaf35c17c681d179












merged with master
2017-09-11T16:03:06+00:00

Robert

2017-09-11T16:03:06+00:00

37865fad65adacae41bff0677651ca0a4d9db974












Fixes #4189@4h Route Duplication
2017-09-11T15:15:49+00:00

Robert

2017-09-11T07:41:03+00:00

f7bc874de79ff9a68aa03523cf653407663e7c55

* Duplication of Route is triggered by link and UI forwarded to edit of duplicatee

     - Changing route, only POST duplicate_referential_line_route --> RoutesController#duplicate
     - Removing route       GET  duplicate_referential_line_route --> RoutesController#duplicate
     - Removing controller action RoutesController#post_duplicate

* Link in Route Decorator depends on new policy RoutePolicy#decorate?

* Adapting specs





* Duplication of Route is triggered by link and UI forwarded to edit of duplicatee

     - Changing route, only POST duplicate_referential_line_route --> RoutesController#duplicate
     - Removing route       GET  duplicate_referential_line_route --> RoutesController#duplicate
     - Removing controller action RoutesController#post_duplicate

* Link in Route Decorator depends on new policy RoutePolicy#decorate?

* Adapting specs







Update of ReferentialsController#new :
2017-09-11T14:21:41+00:00

cedricnjanga

2017-09-11T14:06:42+00:00

8fe9a39516f6fb71545d6329c448680d6f8c75d1

- Add some context to referential and workbench decorator to access current_referential and assign it to the cloned referential
- Add a build_referential method to avoir duplicates of code (in the controller and in the model), need to clean a bit more
- Need to add some Spec features to take into account the functional scope of the current_user





- Add some context to referential and workbench decorator to access current_referential and assign it to the cloned referential
- Add a build_referential method to avoir duplicates of code (in the controller and in the model), need to clean a bit more
- Need to add some Spec features to take into account the functional scope of the current_user







Referential#new_from :
2017-09-05T12:36:47+00:00

cedricnjanga

2017-09-05T12:26:20+00:00

df7552799d16d5686e389e484a00e0a7e8fb4e1d

Added params to certains paths to have the workbench_id in it.
The goal is to have the current workbench_id to assign it when do a Referential#new_from
Then I finished the use of the functional scope to avoid potential errors
I skipped some tests that hve a #TODO so we can easily find them





Added params to certains paths to have the workbench_id in it.
The goal is to have the current workbench_id to assign it when do a Referential#new_from
Then I finished the use of the functional scope to avoid potential errors
I skipped some tests that hve a #TODO so we can easily find them







Fix import status table views and first version for import_messages Refs #4527
2017-09-04T20:59:51+00:00

Luc Donnet

2017-09-04T20:59:51+00:00

0bfb94f1311517838c4d1989e273ce56c605a25a