chouette-core/app/models, branch 4443-edit-metadata

Merge branch 'master' into compliance_control

2017-09-12T13:52:49+00:00

Merge pull request #63 from af83/4189-duplicate-route

2017-09-12T12:46:35+00:00

4189 duplicate route

Edit object#local_id attribute order

2017-09-12T12:23:10+00:00

Refs #4453

Change the import filter to include two inputs and tweak ransack filter to convert date object to dateTime object

2017-09-12T12:04:29+00:00

Refs: #4189@2h; Fixing logical merging issues, preparing PR

2017-09-12T07:10:02+00:00

merged with master

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

Fixes #4189@4h Route Duplication

2017-09-11T15:15:49+00:00

* 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

- 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

ImportMessage: Remove `dependent: :destroy` on :resource association

2017-09-11T10:49:45+00:00

It doesn't really make sense to have a `dependent: :destroy` here. For
one thing, the `Import` class has the necessary `dependent: :destroy`
definitions to remove its associated objects when it gets deleted.

At this point, according to Luc, we don't envision deleting
`ImportResource`s separately from `Import`s.

The other weird thing is that:

* `ImportResource` has many `ImportMessage`s
* `ImportMessage` has one `ImportResource`

With the `dependent: :destroy` set up the way it is here on
`ImportMessage`, we could potentially be deleting an `ImportResource`
with other `ImportMessage` children that would then become orphaned.

For both these reasons, it seems better to remove this trigger.

Refs #4412

Disable uniqueness of name for referential because it stops import for same referential Refs #4415 @1

2017-09-08T14:30:38+00:00