We now only have one field on {versioncontrol_operations} for date, and we need two as we are assuming that we store author and committer independently, so it should be the same for dates.
PS: this started as an sdboyer comment on IRC
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 0001-Issue-1054436-Store-commit-date-and-authoring-date.patch | 14.51 KB | marvil07 |
| #2 | 0001-Issue-1054436-Store-commit-date-and-authoring-date.patch | 3.98 KB | marvil07 |
Comments
Comment #1
marvil07 commentedWell, not really a bug, but something we really want for 2.0 IMHO.
I am starting a patch that would replicate the information on the {versioncontrol_operations}.date to have two fields:
author_dateandcommiter_date.Backends should modify the values later, on a
hook_update_n().Comment #2
marvil07 commentedOk, here the first step: schema change and operation class data members change.
TODO: Change views implementation and default views.
Comment #3
marvil07 commentedComment #4
marvil07 commentedFinally getting this ready.
I pushed the attached patch that:
Update: I forgot to mention that we need to change default views on all dependent projects(i.e. versioncontrol_git, versioncontrol_project)
Comment #5
marvil07 commentedJust to mention the related tickets created: on versioncontrol_project #1203268: Change default views to follow versioncontrol api change on views data and on versioncontrol_git #1203264: Change default views to follow versioncontrol api change on views data
Comment #6
marvil07 commentedI 've just pushed a follow up to fix tests.