Page MenuHomePhabricator

Roughly modularize document rendering in Files
ClosedPublic

Authored by epriestley on Mar 19 2018, 4:42 PM.
Tags
None
Referenced Files
F17626519: D19237.id46064.diff
Thu, Jul 10, 4:44 AM
F17605713: D19237.diff
Wed, Jul 9, 1:51 AM
Unknown Object (File)
May 31 2025, 12:13 PM
Unknown Object (File)
May 25 2025, 2:49 AM
Unknown Object (File)
May 20 2025, 9:50 AM
Unknown Object (File)
May 9 2025, 4:22 PM
Unknown Object (File)
Apr 26 2025, 7:31 AM
Unknown Object (File)
Apr 23 2025, 2:31 PM
Subscribers
None
Tokens
"Like" token, awarded by mydeveloperday.

Details

Summary

Ref T13105. This change begins modularizing document rendering. I'm starting in Files since it's the use case with the smallest amount of complexity.

Currently, we hard-coding the inline rendering for images, audio, and video. Instead, use the modular engine pattern to make rendering flexible and extensible.

There aren't any options for switching modes yet and none of the renderers do anything fancy. This API is also probably very unstable.

Test Plan

Viewwed images, audio, video, and other files. Saw reasonable renderings, with "nothing can render this" for any other file type.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable