Page MenuHomePhabricator

Turn DarkConsole settings into real settings
ClosedPublic

Authored by epriestley on Jun 3 2016, 5:53 PM.
Tags
None
Referenced Files
F15443599: D16029.id.diff
Thu, Mar 27, 5:13 AM
F15440897: D16029.diff
Wed, Mar 26, 3:18 PM
F15416103: D16029.id38581.diff
Thu, Mar 20, 9:18 AM
F15397015: D16029.id38560.diff
Sun, Mar 16, 5:39 PM
F15380181: D16029.id38581.diff
Fri, Mar 14, 1:52 AM
F15374389: D16029.diff
Wed, Mar 12, 6:50 PM
F15338458: D16029.diff
Sun, Mar 9, 10:59 AM
F15282487: D16029.id38560.diff
Tue, Mar 4, 12:15 AM
Subscribers

Details

Summary

Ref T4103. These settings long-predate proper settings and are based on hard-coded user properties. Turn them into real settings.

(I didn't try to migrate the value since they're trivial to restore and only useful to developers.)

Test Plan
  • Toggled console on/off.
  • Swapped tabs.
  • Reloaded page, everything stayed sticky.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Turn DarkConsole settings into real settings.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jun 3 2016, 5:54 PM

I wonder if this could replace darkconsole.always-on since one could turn it on for the 'logged out' or 'default' profile? Just a thought.

I expect to be able to be able to get rid of at least a few other settings like metamta.vary-subjects and metamta.re-prefix and just move them to the global profile.

Stuff like darkconsole.always-on and phabricator.timezone might be removable too, but they enable slightly different behavior than a global default would and may have some boostrapping issues (e.g., we might emit a log early on that needs the timezone defined, before we have a chance to build it from storage).

This revision was automatically updated to reflect the committed changes.