Page MenuHomePhabricator

[SPIKE] Evaluate performance of using visual diff "engine" for surfacing real-time feedback
Closed, ResolvedPublicSpike

Description

There are two approaches we are currently considering for identifying what someone has added, moved, or removed during the course of an edit session:

  • Approach #1: Use VE's "native" transaction stack/logging
  • Approach #2: Use the visual diff "engine"

...this task involves investigating approach #2 with the goal of understanding what – if any – changes would need to be made to the visual diff "engine" for it to be performant enough to be used to offer real-time feedback about the changes they're in the midst of making.

Event Timeline

ppelberg moved this task from To Triage to Triaged on the VisualEditor board.
ppelberg moved this task from Untriaged to Upcoming on the Editing-team board.
VPuffetMichel renamed this task from [SPIKE] Evaluate performance of using visual diff "engine" for surfacing real-time feedback to [edit check] [SPIKE] Evaluate performance of using visual diff "engine" for surfacing real-time feedback.Dec 8 2022, 1:38 PM
ppelberg renamed this task from [edit check] [SPIKE] Evaluate performance of using visual diff "engine" for surfacing real-time feedback to [SPIKE] Evaluate performance of using visual diff "engine" for surfacing real-time feedback.Dec 12 2022, 5:54 PM
Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptJan 3 2023, 4:38 PM

DECIDED
Per what @Esanders and I talked about offline today, we're going to prioritize work on this task only if we do NOT think the output from T323145 is going to be reliable enough.

As such, I'm moving this task to the backlog for now.

Meeting notes from today:

  • Avoid unless we decide transaction-based isn't good enough
  • We know what the diff output looks like already (show changes in save dialog)

Per above and @ppelberg's previous comment, I think we can close this.