Repository navigation
add creation_time to lock definition - #278
Conversation
|
I think this was discussed in the past and I gently objected against :-) My objection was and is: the only value that matters for a lock is the expiration time, not the creation time. In addition, when an application (typically via WOPI) holds a lock, it can refresh it "forever", until a user works on the file, making the timing information essentially irrelevant. What is the purpose of bringing this information to the average user? IMHO users would be induced to make (likely wrong) assumptions by knowing that a file was locked "1 hour ago" or "1 minute ago", whereas they should just be informed that "a file is locked by user abc" or "by app xyz". |
diocas
left a comment
There was a problem hiding this comment.
It's an optional field. Might be useful to display that info for users, in case a file has been locked for a long time, might lead to the realization that it was forgotten.
@aduffeck @micbar @butonic any objections? :)