Change Details

See PHI1224, which requests support for linking to source files in a way that makes access via an external editor easier. Previously, see T5378. My plan of attack here is: - Convert existing Doorkeeper rules (JIRA and Asana) to use the new extension point. See also T13285. - Begin recognizing and specializing the rendering of full `https://install.com/diffusion/x/y/z.c` URIs, similar to how `https://install.com/T123` URIs are now specialized. - Provide an alternate mechanism for this rendering rule, `{src ...}`. - Add options to control layout and behavior.

See PHI1224, which requests support for linking to source files in a way that makes access via an external editor easier. Previously, see T5378. My plan of attack here is: - Convert existing Doorkeeper rules (JIRA and Asana) to use the new extension point. See also T13285. - Begin recognizing and specializing the rendering of full `https://install.com/diffusion/x/y/z.c` URIs, similar to how `https://install.com/T123` URIs are now specialized. - Provide an alternate mechanism for this rendering rule, `{src ...}`. - Add options to control layout and behavior. Once this lands, both `{src ...}` and the new `uri`, `{uri}`, and `<uri>` rules should be documented.

See PHI1224, which requests support for linking to source files in a way that makes access via an external editor easier. Previously, see T5378. My plan of attack here is: - Convert existing Doorkeeper rules (JIRA and Asana) to use the new extension point. See also T13285. - Begin recognizing and specializing the rendering of full `https://install.com/diffusion/x/y/z.c` URIs, similar to how `https://install.com/T123` URIs are now specialized. - Provide an alternate mechanism for this rendering rule, `{src ...}`. - Add options to control layout and behavior. Once this lands, both `{src ...}` and the new `uri`, `{uri}`, and `<uri>` rules should be documented.