epriestley 2b19f91936 Allow Doorkeeper references to have multiple display variations (full, short, etc.) ... Summary: Ref T13102. An install has a custom rule for bridging JIRA references via Doorkeeper and would like to be able to render them as `JIRA-123` instead of `JIRA JIRA-123 Full JIRA title`. I think it's reasonable to imagine future support upstream for `JIRA-123`, `{JIRA-123}`, and so on, although we do not support these today. We can take a small step toward eventual support by letting the rendering pipeline understand different view modes. This adds an optional `name` (the default text rendered before we do the OAuth sync) and an optional `view`, which can be `short` or `full`. Test Plan: I tested this primarily with Asana, since it's less of a pain to set up than JIRA. The logic should be similar, hopefully. I changed `DoorkeeperAsanaRemarkupRule` to specify `name` and `view`, e.g `'view' => (mt_rand(0, 1) ? 'short' : 'full')`. Then I made a bunch of Asana references in a comment and saw them randomly go short or long. Maniphest Tasks: T13102 Differential Revision: https://secure.phabricator.com/D19215		2018-03-13 11:29:52 -07:00
..
audio/basic	Add a few more sounds	2017-04-19 13:47:23 -07:00
css	When proxying an "{image ...}" image fails, show the user an error message	2018-03-08 07:03:26 -08:00
externals	Use a tokenizer, not a gigantic poorly-ordered "<select />", to choose repositories in Owners	2018-03-07 20:57:24 -08:00
favicons	Dynamically composite favicons from customizable sources	2018-03-12 15:28:41 -07:00
image	Uh, update Phabricator login image	2017-08-11 13:37:26 -07:00
js	Allow Doorkeeper references to have multiple display variations (full, short, etc.)	2018-03-13 11:29:52 -07:00