Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle missing language support in notebook cell #187516

Closed
rebornix opened this issue Jul 10, 2023 · 0 comments · Fixed by #190695
Closed

Handle missing language support in notebook cell #187516

rebornix opened this issue Jul 10, 2023 · 0 comments · Fixed by #190695
Assignees
Labels
insiders-released Patch has been released in VS Code Insiders notebook-language Bugs related to general interaction with languages on-testplan
Milestone

Comments

@rebornix
Copy link
Member

Currently if we don't find language provider for cells, we would fall back to plaintext, this will make the document dirty immediately. We should actually respect the language metadata, show a warning on the cell status bar language picker and ask users to install language extensions for it.

@rebornix rebornix self-assigned this Jul 10, 2023
@rebornix rebornix added the notebook-language Bugs related to general interaction with languages label Jul 10, 2023
@rebornix rebornix added this to the July 2023 milestone Jul 10, 2023
@rebornix rebornix modified the milestones: July 2023, August 2023 Jul 24, 2023
@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Aug 17, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Oct 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
insiders-released Patch has been released in VS Code Insiders notebook-language Bugs related to general interaction with languages on-testplan
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants