Page MenuHomePhabricator

Don't handle JIRA/Asana URIs with anchors or query parameters in a special way (with Doorkeeper)
AbandonedPublicDraft

Authored by epriestley on Jun 19 2019, 5:44 PM.
Tags
None
Referenced Files
F12825050: D20591.diff
Thu, Mar 28, 8:43 AM
Unknown Object (File)
Sat, Mar 23, 12:45 PM
Unknown Object (File)
Sat, Mar 23, 12:45 PM
Unknown Object (File)
Sat, Mar 23, 12:45 PM
Unknown Object (File)
Sat, Mar 23, 4:26 AM
Unknown Object (File)
Sun, Mar 10, 5:43 AM
Unknown Object (File)
Tue, Mar 5, 1:13 AM
Unknown Object (File)
Feb 6 2024, 6:02 AM
Subscribers
None

Details

Summary

Ref T13291. See PHI1312. Currently, if you link to a JIRA or Asana issue with an anchor (#asdf) or query parameters (?a=b), we:

  • treat the link as an external object reference and attempt a lookup on it;
  • if the lookup succeeds, we discard the fragment or parameters when re-rendering the rich link (with the issue/task title).

Particularly, the re-rendering part uses the canonical URI of the object, and can discard these parameters/fragments, which is broken/bad.

As a first pass at improving this, just don't apply special behavior for links with anchors or parameters -- simply treat them as links.

In some future change, we could specialize this behavior and permit certain known parameters or anchors or something, but these use cases are likely fairly marginal.

Test Plan

Before:

Screen Shot 2019-06-19 at 10.38.02 AM.png (563×542 px, 74 KB)

After:

Screen Shot 2019-06-19 at 10.39.37 AM.png (567×550 px, 74 KB)

Diff Detail

Repository
rP Phabricator
Branch
close1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 22993
Build 31558: Run Core Tests
Build 31557: arc lint + arc unit