Page MenuHomePhabricator

[Epic] Some import validation should only run on the most recent revision.
Open, Needs TriagePublic

Description

This task is complete when FileImporter applies relaxed validation on older revisions. For example, duplicate or blank content should be allowed.

Event Timeline

I'm not sure what to do with this ticket, because I don't understand what "most recent version" is supposed to mean.

awight renamed this task from Issues that might only be relevant for the most recent version to [Epic] Issues that might only be relevant for the most recent version.Sep 10 2019, 10:07 PM

I'm not sure what to do with this ticket, because I don't understand what "most recent version" is supposed to mean.

It's the file version that was uploaded most recently. In this list of file versions (example from duplicate content related subtask) it's the topmost file version. It makes sense that certain checks, including check on duplicate files, are run on this topmost file version, but it doesn't seem wanted to me that older versions are also checked.

awight renamed this task from [Epic] Issues that might only be relevant for the most recent version to Some import validation should only run on the most recent revision..Sep 11 2019, 11:12 AM
awight updated the task description. (Show Details)

I'm not sure what to do with this ticket, because I don't understand what "most recent version" is supposed to mean.

It's the file version that was uploaded most recently. In this list of file versions (example from duplicate content related subtask) it's the topmost file version. It makes sense that certain checks, including check on duplicate files, are run on this topmost file version, but it doesn't seem wanted to me that older versions are also checked.

Thank you, I hadn't noticed that common theme!

awight renamed this task from Some import validation should only run on the most recent revision. to [Epic] Some import validation should only run on the most recent revision..Sep 11 2019, 11:13 AM