[FEATURE]: manage notebook migration at the cell level rather than the notebook level #1477
ericvergnaud
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there an existing issue for this?
Problem statement
The current implementation skips notebooks for which the default language is not yet supported (Scala, R).
This is sub-optimal because these notebooks may contain cells that we can migrate: Python, SQL and %run
Proposed Solution
Enhance NotebookMigrator such that it only skips unsupported cells, rather than entire notebooks.
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions