[09:49:16] Krinkle: Re traces in log messages, https://gerrit.wikimedia.org/r/c/mediawiki/core/+/730695/3/includes/jobqueue/jobs/RefreshLinksJob.php#61 [09:49:41] I'm not sure what you mean by using the "exception" key. There is no exception there... Should I used "exception.trace" directly? [09:54:52] 'exception' => new RuntimeException() would be the recommendation at https://www.mediawiki.org/wiki/Manual:Structured_logging#Add_structured_data_to_logging_context fwiw [12:22:12] hello, apparently gerritbot forgot to link my patch in the related phab taks, or perhaps I did something wrong? https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cite/+/735369 [12:22:57] PeterBowman: you have an empty line between the Bug: and Change-Id: lines [12:23:22] oh right, I'll remove that, thanks [12:32:08] is there any "standard" state management system already used in the client-side JS? [14:40:37] "is there any "standard" state..." <- by state do you mean localStorage/cookies/mw.storage/user prefs? or something else [14:41:09] no, i mean like some kind of MVC thing [14:41:54] at lot of the JS I'm wrestling with is getting a bit hairy, and I was wondering if there's something already "normal" for that kind of thing [14:46:21] (currently, I'm looking at the proofread page edit form, which needs to configure itself based on a few user toggles) [15:27:10] OO.EventEmitter maybe?