GitHub user sshiv012 added a comment to the discussion: [Notebook Migration] Keeping the notebook mapping and Jupyter panel for Python file input
I like B as well, AI should get better and inexpensive in doing such non-deterministic search problems, the mapping helps users understand and verify the migration. My main concern is treating LLM-generated line ranges as the source of truth. Could we preserve the original script and validate the ranges against it before building cells? Overlaps may be legitimate when the same code contributes to multiple operators, while gaps should remain visible as unmapped code rather than disappear. It would also be nice to distinguish “this operator came from these lines” from “these lines can run independently as a notebook cell,” since imports and shared state may cross those boundaries. GitHub link: https://github.com/apache/texera/discussions/8489#discussioncomment-18806969 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
