Page MenuHomePhabricator

When an inline was left on a rendered DocumentEngine document, don't include an email context patch
ClosedPublic

Authored by epriestley on May 12 2020, 9:09 PM.
Tags
None
Referenced Files
F18236903: D21242.id.diff
Wed, Aug 20, 8:37 PM
F18222597: D21242.diff
Tue, Aug 19, 9:22 PM
F18112335: D21242.diff
Tue, Aug 12, 4:25 PM
F17898904: D21242.id50586.diff
Jul 29 2025, 8:25 AM
F17843995: D21242.id50586.diff
Jul 27 2025, 1:34 AM
F17843106: D21242.id50589.diff
Jul 27 2025, 12:29 AM
F17840404: D21242.id.diff
Jul 26 2025, 9:07 PM
F17825262: D21242.diff
Jul 26 2025, 6:14 AM
Subscribers
None

Details

Summary

Ref T13513. If you leave an inline on line 20 of a Jupyter document, we currently render context around *raw* line 20, which is inevitably some unrelated piece of JSON.

Instead, drop this context. (Ideal behavior would be to render context around Jupyter block 20, but that's a whole lot of work.)

Test Plan
  • On Jupyter changes and normal source changes, made and submitted inline comments, then viewed text and HTML mail.
  • Saw no context on Jupyter comments (instead of bad context), and unchanged behavior (useful context) on normal source changes.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable