KEMBAR78
Explore supporting cross cell NES in notebooks · Issue #255704 · microsoft/vscode · GitHub
Skip to content

Explore supporting cross cell NES in notebooks #255704

@DonJayamanne

Description

@DonJayamanne
  • 🏃 Experiment to enable the Jupytext alternative Notebook format in NES
    • Enable this
  • Telemetry: survival rate
    • Compare survival/telemetry for regular NES vs regular notebook cells vs unified notebook
  • Tests (scenarios for cross cell NES, etc),
  • Improve Trigger Events for cross cell NES
    • Better triggers for NES: alt format gives us a better "Cursor_move" event, what else?)
  • Explore enabling suggestions for other cells
    • we filter them out today, and they are cached
    • do we have other ways to suggest actions to other cells
      • Can we trigger nes command on other cells
      • What do we need to make this happen for other cells?
      • Can we implement short term solutions?
  • Improvements authoring stests for notebooks
    • Find whats missing and add it
  • Improve issue reporting for notebooks
    • Existing command works well
    • Added a new command to report with required data as well
  • Golden Scenarios for cross cell NES https://github.com/microsoft/vscode-internalbacklog/issues/5701

Add the following setting

"github.copilot.chat.advanced.notebook.alternativeNESFormat.enabled": true,
"github.copilot.chat.notebook.enhancedNextEditSuggestions.enabled":true

When/How to display/trigger NES in other cells

  • Display Go To Next Edit: User in Cell 1 and there are suggested changes in Cell 2
  • Should we display NES in cells after user edits a cell and runs it and then advances to the next cell
    • Users workflow is make changes to cell 1, run this
    • Should we wait till user sets focus to next cell in order to trigger NES for the next cell?
    • Can we instead proactively let user know that there are possible changes in next cell?
  • Auto trigger NES completions when user sets focus to next cell after having modified another cell in same doc
    • Assume user changes cell 1
      • User sets focus or uses down arrow to go to next cell
      • We should trigger NES in this next cell
    • Assume user changes cell 1, next runs the cell
      • User keeps running the cell and tweaking cell 1, but never updates any other text document
      • After 30 minutes user goes to cell 10
      • We should trigger NES as user was still editing this notebook & didn't modify anything else in the interim

Sub-issues

Metadata

Metadata

Assignees

Labels

NESIssues related to the next edit suggestions featurefeature-requestRequest for new features or functionalitynotebookon-testplan

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions