zyratlo opened a new pull request, #8631: URL: https://github.com/apache/texera/pull/8631
### What changes were proposed in this PR? The migration tool now accepts Python files as well as notebooks, with R and folders to follow, but the workspace still told users they were looking at a "Jupyter Notebook". A user who uploaded a `.py` saw a panel with that title, a button labelled "expand Jupyter notebook", and a confirmation asking whether to delete "this workflow's Jupyter notebook". The display strings that name the input type are now generic: the panel header and its iframe title read "Uploaded Source Code", the delete tooltip and confirmation say "source code", and the toolbar button says "expand uploaded source code". Four notifications that named the input the same way were updated too. The toolbar button used the Jupyter logo, which reads wrong next to a generic label. It now uses the `code` icon from ng-zorro, matching every other button in that toolbar. That made `jupyter-logo.svg` unused, so it is deleted along with its `.licenserc.yaml` exclude and its line in `frontend/LICENSE-binary`. The attribution block itself stays, since `tool_popup_diagram.png` still carries the Jupyter logo in the import modal. Display strings only. Internal names (`JupyterPanelService`, `notebookFileName`, the `notebook` table, the `/notebook-migration` endpoints) are unchanged and still accurate, since a script really is converted into a notebook. The import modal is also unchanged: its tabs name their own input correctly. ### Any related issues, documentation, discussions? Closes #8543 Parent-issue #4301 ### How was this PR tested? No new tests. The change is copy plus one icon, with no behavior to cover. Verified the UI changes in local deployment. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
