Last modified: 2014-02-24 18:25:29 UTC
Please add a wgCurRevisionTimestamp to the mw.config set of variables as it would be more efficient than an API call just for that information and is a fairly frequently used piece of information (when attempting to avoid edit conflict issues.
It would help if, rather than only presenting a potential solution, you also described your problem (i.e., your use-case). Feel free to paste example code or links to code here.
https://github.com/azatoth/twinkle/issues/175 https://github.com/WPAFC/afch/issues/153 Are two issues I know of where such a variable would be more efficient, although not for the edit conflict reason. Having this parameter would also give something to compare the current timestamp from the API with against to help resolve issues like: https://github.com/WPAFC/afch/issues/30 https://github.com/WPAFC/afch/issues/156
I might recommend building a cleaner JS interface for 'currently displayed revision information' rather than just adding more and more globals...
Another solution is bug 32037: detect edit conflicts with the revision id, not with a timestamp
(In reply to comment #4) > Another solution is bug 32037: detect edit conflicts with the revision id, > not with a timestamp Which still doesn't solve use cases like the first two I mentioned: https://github.com/azatoth/twinkle/issues/175 https://github.com/WPAFC/afch/issues/153
