Page MenuHomePhabricator

When creating an inline, save the current document engine
ClosedPublic

Authored by epriestley on May 12 2020, 7:19 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 15, 6:32 AM
Unknown Object (File)
Nov 30 2023, 1:01 AM
Unknown Object (File)
Nov 25 2023, 11:29 PM
Unknown Object (File)
Nov 16 2023, 5:00 PM
Unknown Object (File)
Nov 15 2023, 11:33 AM
Unknown Object (File)
Nov 13 2023, 6:39 PM
Unknown Object (File)
Nov 11 2023, 8:32 AM
Unknown Object (File)
Oct 29 2023, 11:38 PM
Subscribers
None

Details

Summary

Ref T13513. As part of inline metadata, save the document engine the change is being rendered with.

This will allow other parts of the UI to detect that an inline was created on a Jupyter notebook but is being rendered on raw source, or whatever else.

The immediate goal is to fix nonsensical inline snippet rendering in email on Jupyter notebooks.

Test Plan
  • Created inlines and replies on normal soure code, saw no document engine annotated in the database.
  • Created inlines and replies on a Jupyter notebook rendered in Jupyter mode, saw "jupyter" annotations in the database.
  • Swapped document engines between Jupyter and Source, etc.

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.May 12 2020, 9:25 PM
This revision was automatically updated to reflect the committed changes.