Page MenuHomePhabricator

Have Badges use getMostOpenPolicy for View
ClosedPublic

Authored by chad on Jul 24 2015, 4:40 PM.
Tags
None
Referenced Files
F14065506: D13702.diff
Tue, Nov 19, 4:57 AM
F14042886: D13702.diff
Tue, Nov 12, 6:47 AM
F14000823: D13702.diff
Fri, Oct 25, 1:23 AM
F13993750: D13702.id33121.diff
Wed, Oct 23, 1:11 AM
F13992026: D13702.diff
Tue, Oct 22, 1:58 PM
F13964220: D13702.id33114.diff
Oct 15 2024, 7:56 PM
F13964219: D13702.id.diff
Oct 15 2024, 7:56 PM
F13964218: D13702.diff
Oct 15 2024, 7:56 PM
Subscribers

Details

Summary

Fixes T8938. Sets by default for new badges, getMostOpenPolicy. Removes ability to edit viewPolicy.

Test Plan

Create a new badge, see its public, assign it, log out, still able to view it.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

chad retitled this revision from to Have Badges use getMostOpenPolicy for View.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added reviewers: epriestley, btrahan.
btrahan edited edge metadata.

In theory, there may exist some badges that got set to some restrictive view policy in the wild. I think you'd want to write a migration script to migrate these things to more open, except that's kind of funky. Anyway, just an FYI you probably already knew I guess...

This revision is now accepted and ready to land.Jul 24 2015, 5:44 PM

We should also drop the column in the table at some point.

Yeah, nothing reads it anymore. Policy infrastructure doesn't depend on it existing because some objects don't have an editable view policy.

This revision was automatically updated to reflect the committed changes.