You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Notebook Migration] Support migrating R folders #9386
R projects often span several files, with one script calling functions that others define. This issue tracks letting users convert a local folder of R files into one Texera workflow, as the folder part of #8009 and the R counterpart of the Python folder support from #8767. Converting the files one at a time would lose the relationships between them, which is the point of migrating a project as a whole. It should reuse as much of the Python folder pipeline as possible rather than build a second one.
Proposed Solution or Design
The import modal gets an R Folder tab using the same directory picker, file limits and size limits as the Python Folder tab. The .R files are assembled into one document with a banner line per file and continuous line numbers, with a folder layout sent ahead of it; other files in the folder are named in the layout but never read. This needs R folder prompts and an R folder worked example, since the current folder prompts teach Python, and the prompt set gains a folder entry for each language. As with Python, the model names the entry point, the derived notebook shows only that file, and mapping ranges point at its call sites. The tab is gated on rNotebookMigrationEnabled like the other R options, and this starts after #8912 and #8963 merge.
Activity
zyratlo commentedon Nov 9, 2026
/parent-issue #8009
zyratlo commentedon Nov 9, 2026
/take
feat(notebook-migration): add r files to the import modal (apache#8963)
feat(notebook-migration): add r folders to the import modal (apache#9427