GitHub user sshiv012 added a comment to the discussion: [Notebook Migration WIP] Adding R support
I like the direction of starting with the simpler version first. Reusing the existing migration pipeline and only making the prompt/operator construction language-specific seems like the right boundary. For mixed folders, I’d prefer rejecting mixed R/Python input in the first version, but I think we should design the implementation so language is a parameter rather than adding R-specific branches throughout the tool. For the Jupyter panel, I also agree that read-only R notebook display should not depend on having an R kernel. Kernel support feels like a separate capability that we should only introduce once we actually support executing cells from the panel. One thing I’d be interested in is how language is detected for notebooks vs files/folders. For files the extension is straightforward, but for notebooks I think kernel/language metadata should probably be the default signal, with a fallback if metadata is missing or ambiguous? GitHub link: https://github.com/apache/texera/discussions/8866#discussioncomment-18769175 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
