Page MenuHomePhabricator

Make hidden and locked configuration even more explicit
ClosedPublic

Authored by epriestley on Jan 28 2016, 3:29 PM.
Tags
None
Referenced Files
F13229493: D15128.id36526.diff
Mon, May 20, 4:48 PM
F13183938: D15128.diff
Fri, May 10, 1:24 PM
Unknown Object (File)
Tue, May 7, 2:44 AM
Unknown Object (File)
Sun, Apr 28, 5:34 PM
Unknown Object (File)
Apr 13 2024, 2:13 PM
Unknown Object (File)
Apr 12 2024, 12:33 AM
Unknown Object (File)
Apr 5 2024, 1:49 PM
Unknown Object (File)
Mar 24 2024, 3:32 AM
Subscribers
None
Tokens
"Like" token, awarded by Luke081515.2.

Details

Summary

A user in IRC seemed very confused by this, and worked extremely hard to shoot themsevles in the foot by manually writing locked configuration to the database.

Try to explain why configuration is locked better.

Test Plan

Mostly reading.

Screen Shot 2016-01-28 at 7.27.24 AM.png (788×1 px, 138 KB)

Screen Shot 2016-01-28 at 7.27.18 AM.png (736×1 px, 122 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make hidden and locked configuration even more explicit.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Workflows are just get and set.
chad edited edge metadata.
This revision is now accepted and ready to land.Jan 28 2016, 4:05 PM
This revision was automatically updated to reflect the committed changes.