Page MenuHomePhabricator

Allow Doorkeeper references to have multiple display variations (full, short, etc.)
ClosedPublic

Authored by epriestley on Mar 13 2018, 6:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 25, 3:31 AM
Unknown Object (File)
Fri, Apr 5, 9:53 PM
Unknown Object (File)
Mar 22 2024, 3:53 PM
Unknown Object (File)
Feb 17 2024, 5:04 AM
Unknown Object (File)
Feb 14 2024, 8:24 PM
Unknown Object (File)
Dec 26 2023, 8:21 PM
Unknown Object (File)
Dec 25 2023, 6:08 PM
Unknown Object (File)
Dec 24 2023, 7:52 AM
Subscribers
None

Details

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.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Mar 13 2018, 6:29 PM
This revision was automatically updated to reflect the committed changes.