-
Notifications
You must be signed in to change notification settings - Fork 298
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
Display errors against the actual code (squiggles, etc) instead of just displaying the error as cell output (Native Notebook) #4589
Labels
feature-request
Request for new features or functionality
notebook-output
notebook-workflow
Issues that interrupt expected or desirable behavior
*out-of-scope
Posted issue is not in scope of VS Code
Comments
DonJayamanne
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Feb 1, 2021
DonJayamanne
changed the title
Highlight the line that has errors instead of just displaying the error
Display errors against the actual code (squiggles, etc) instead of just displaying the error as cell output (Native Notebook)
Feb 1, 2021
DonJayamanne
added
enhancement
and removed
bug
Issue identified by VS Code Team member as probable bug
labels
Feb 1, 2021
We do some of this in the interactive window with our links. Does normal python do this for debugging? I guess the callstack window provides the location. |
greazer
added
the
notebook-workflow
Issues that interrupt expected or desirable behavior
label
Aug 4, 2021
moving to triage as this came up recently |
greazer
added
feature-request
Request for new features or functionality
and removed
enhancement
labels
May 4, 2022
IanMatthewHuff
added
the
notebook-intellisense
Intellisense & other language features in notebook cells for any language
label
Aug 12, 2022
@IanMatthewHuff i think this falls under execution and errors & display of the errors, not intellisense, let me know if thats ok |
DonJayamanne
removed
the
notebook-intellisense
Intellisense & other language features in notebook cells for any language
label
Aug 15, 2022
Closing as out of scope, not requested by anyone and no upvotes |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feature-request
Request for new features or functionality
notebook-output
notebook-workflow
Issues that interrupt expected or desirable behavior
*out-of-scope
Posted issue is not in scope of VS Code
Run a cell with errors, & i get the details of the error in the output.
I would like a deeper integration with VS Code so that I see the error in the cell itself.
Else it still feels like i'm using a terminal, running code in a terminal, looking at the output & then translating that output error & looking at my editor to find that faultly code.
I'm using VS Code for because i like its editor features, but this still feels very much like compiling code in a terminal.
The text was updated successfully, but these errors were encountered: