| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The condition to remove the right dates was not well implemented
|
|
|
|
|
|
We also needed to take remove the right time table dates when we update day types :
- excluded dates that are out of day types
- included dates that are in day types and in periods
|
|
|
|
Didn't like how `#initialize` takes a different type for `klass` than
`.methods_by_class`. Make these types and values uniform. If we need to
change it, we should make a separate mechanism to do so. I think.
Refs #4401
|
|
Allows us to get all `ModelAttribute`s given a certain class name.
Needed an `#==` method to be able to test object equality more easily so
I added one in.
I don't like that the `klass` is a lowercase symbol and the `klass`
attribute to `.methods_by_class` is a constantized string. Want to
correct that and make them uniform. Only did it this way because that's
how it was suggested in the ticket.
Refs #4401
|
|
Robert argues that the class variable is not ideal because its value
gets shared with subclasses, violating the Liskov substitution
principle:
17:44:23 < robert> ```133] pry(main)> class A; @@greeting = :hello end
17:44:23 < robert> => :hello
17:44:23 < robert> [134] pry(main)> class B < A; end
17:44:23 < robert> => nil
17:44:23 < robert> [135] pry(main)> B.class_variable_get '@@greeting'
17:44:23 < robert> => :hello
Instead, go with his suggestion to use a class instance variable
instead, which gives us the same amount of availability of the `all`
list while not sharing it indiscriminately and making it easier to test.
Refs #4401
|
|
|
|
A method that returns a string representation of the attribute, in the
form `:class#:name".
This will be used to store a reference to the attribute in the database.
For example, a validation will reference a `ModelAttribute` in a
database column using this `#code` string.
Refs #4401
|
|
We want to define `ModelAttribute`s for an initial set of `Chouette`
models:
* Chouette::Route
* Chouette::JourneyPattern
* Chouette::VehicleJourney
* Chouette::Footnote
* Chouette::TimeTable
* Chouette::RoutingConstraintZone
I added these by looking at the `schema.rb` as well as some form views
for these models. Given that information, I made some guesses about what
attributes it might make sense to add here.
We want to end up with a collection of only editable attributes for
these models, so this excludes things like `created_at`, foreign keys,
and programmatically set fields.
This is my guess at what those fields are. We can refine the list later.
We'll be using this list for Compliance Control to get a set of fields
of a given type in order to create custom validations using those
fields.
Refs #4401
|
|
|
|
When `ModelAttribute` instances are added to `@@all` directly in the
class, the test breaks. Make it a little more robust by checking change
in array size instead of total size.
Refs #4401
|
|
This new class will allow us to generate a list of all editable fields
in all our models including the type of each field.
We need this for Compliance Control, in order to get a list of fields or
models & fields that can be selected to validate a given model
validation check. The crucial bits here are the models, fields, and the
types of those fields. These need to be defined (manually at least to
begin with), accessible, and filterable.
Refs #4401
|
|
af83/4555-rake-referential_create--update-Route#wayback-values
referential.rake: Update `Route#wayback` values
|
|
The possible values for this field changed in
2fa3be1518da4f471d614832f80526e074983195 to `outbound` and `inbound`.
Update them accordingly in this Rake task, otherwise it fails.
Refs #4555
|
|
|
|
|
|
|
|
|
|
Refs #4391
|
|
|
|
|
|
Refs #4543
|
|
Refs #4543
|
|
Refs #4543
|
|
Refs #4543
|
|
Refs #4543
|
|
Refs #4543
|
|
|
|
Fixes: #4431@0.16666666666666666h;
|
|
4446 spec features api keys
|
|
|
|
4466 compliance control sets
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Make failing /delete_api_key_feature_spec pending
- Seems Capybara only sees html from the partial api_keys/_form, but not
the parent api_keys/edit, which happens to contain the delete link :(
* ApiKeyPolicy adapted
- update? depends on record's organisation as no referential present
- create? depends on user's permission only as organisation will be correct anyway
|
|
needs of #4446
|
|
|
|
|
|
|
