| Age | Commit message (Collapse) | Author |
|
Refs #4585
|
|
|
|
Refs #4585
|
|
Refs #4580
|
|
Refs #4581
|
|
af83/3520-workbench--add-output-association-to-ReferentialSuite
3520 workbench add output association to referential suite
|
|
ImportPolicy changing *.imports →' imports.*
|
|
|
|
|
|
Since all `Workbench`es must have an associated `ReferentialSuite` via
`output`, if none is provided when creating a new `Workbench`, create
one automatically.
This is done in a `before_validation` callback (eck, AR callbacks).
In order for our prior 'should validate_presence_of' test to continue to
work, we have to work around the new callback, otherwise Shoulda can't
set `output` to `nil` to run its expectation and the test fails.
Refs #3520
|
|
Ensure all workbenches always have an associated `ReferentialSuite` by
validating presence of the `output` attribute.
In order to pass the 'should have a valid factory' test, we need to
define a `ReferentialSuite` factory and set up a default association on
`output` in the `Workbench` factory.
We also need to add set `output` when creating a `Workbench` in
`spec/support/referential.rb`, otherwise we get a validation error that
breaks the tests. Clean up the formatting of that call. In order to pass
a `ReferentialSuite`, I just create one above, but I'm not sure if I
should be using a `find_or_create` mechanism like the other associated
objects do above.
Refs #3520
|
|
The `output` attribute should be a `ReferentialSuite`.
Refs #3520
|
|
`ReferentialSuite` has many `Referential`s. Need to add a foreign key
column to the `referentials` table to allow that to work.
Refs #3519
|
|
This model is responsible for collecting referentials in order to merge
them into a single referential.
* `new` corresponds to a referential in the process of being validated
* `current` corresponds to the most recently validated referential
Refs #3519
|
|
Object ID
=> Change the way provider_id in constructed to replace every space with an underscore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Refs #4467
|
|
|
|
|
|
|
|
4189 duplicate route
|
|
Refs #4453
|
|
convert date object to dateTime object
|
|
|
|
|
|
* 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
|
|
- 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
|
|
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
|
|
referential Refs #4415 @1
|
|
|
|
|
|
|
|
performs a real referential clone. Refs #4335
|
|
Refs #4406
|
|
|
|
files. Refs #4259
|
|
Refs #4390
|
|
Refs #4391
|
|
|
|
Refs #4388
|
|
|
|
|
|
Calendar#index date filter (ransackable scope)
I realized that we could submit the form with incomplete date which caused an 500 error.
So I added a small JS script to prevent user from subnitting filter form with incomplete dates
Since it was really similar with previous work I added two folders : /helpers & /filters to be more DRY
The JS files are loaded in 4 views for the moment, hence the update in the assets.rb file
|