Page MenuHomePhabricator

Separate the "{img ...}" remarkup rule into separate parse and markup phases
ClosedPublic

Authored by epriestley on Mar 8 2018, 1:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, May 3, 8:10 AM
Unknown Object (File)
Mon, Apr 29, 5:57 PM
Unknown Object (File)
Thu, Apr 25, 2:11 AM
Unknown Object (File)
Mon, Apr 22, 3:15 PM
Unknown Object (File)
Fri, Apr 19, 7:32 PM
Unknown Object (File)
Wed, Apr 10, 8:20 AM
Unknown Object (File)
Apr 7 2024, 11:04 AM
Unknown Object (File)
Apr 3 2024, 9:00 PM
Subscribers
None

Details

Summary

Ref T13101. Ref T4190. This rule is currently single-phase but I'd like to check for a valid proxied image in cache already and just emit an <img ... /> tag pointing at it if we have one.

To support batching these lookups, split the rule into a parse phase (where we extract URIs) and a markup phase (where we build tags).

Test Plan

Used {img ...} in Remarkup with no apparent behavioral changes. (This change should do nothing on its own.)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley created this revision.
  • Improve word use in comment.
This revision was not accepted when it landed; it landed in state Needs Review.Mar 8 2018, 3:03 PM
This revision was automatically updated to reflect the committed changes.