Page MenuHomePhabricator

User should receive a nicer exception when selecting an invalid application policy like "Can Use Application: No One"
Open, WishlistPublic

Description

When setting application policy Can Use Application to value No One, the following exception is printed:

I do not see a way to set this value without viewing it on the Web-UI. So this looks like being a useless option, isn't it?

Event Timeline

Judge created this task.Sep 25 2014, 3:41 PM
Judge raised the priority of this task from to Needs Triage.
Judge updated the task description. (Show Details)
Judge added a project: Phabricator.
Judge added a subscriber: Judge.
epriestley triaged this task as Wishlist priority.Sep 25 2014, 3:58 PM
epriestley edited projects, added Policy; removed Phabricator.
epriestley added a subscriber: epriestley.

We use the same policy control everywhere, but some policies aren't meaningful in some contexts. We could do a better job about hiding them, although that would also create some confusion ("why can't I select 'no one' in this dropdown?"). Since it's fairly obvious why "no one" doesn't work with the current workflow once you save, I don't think this is too bad. It could be a bit cleaner, but the ideal version of this would look roughly the same ("no one" present, tells you why you can't use it when selected, just looks less exception-ey).

epriestley renamed this task from "Can Use Application" policy value "No One" useless? to User should receive a nicer exception when selecting an invalid application policy like "Can Use Application: No One".Dec 13 2016, 11:40 AM