curationexperts / epigaea / 2343

90%

Pull #836

travis-ci

Make sure fields get marked as dirty if they change. Story #122

I overrode the getter and setter methods for the ordered fields to keep
track of their order in secondary fields, but that caused a problem.
Even though those fields appeared to be correct in the UI, I noticed
that the `description` and `ordered_descriptions` fields were out of
sync in the fedora console.

The overrides to the getters and setters messed up the logic that
determines whether or not a field is marked dirty.

I wrote a spec to make sure that both the original field and its
secondary ordering field will be marked dirty if the field is updated,
and then moved the `super` call to the top of the setter method, which
solves the problem with the logic for dirtiness.

2 of 2 new or added lines in 1 file covered. (100.0%)

2741 of 3026 relevant lines covered (90.58%)

111.27 hits per line