fix: add null check to inline controller on change #781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: add null checks before accessing editor properties
The code to track copy action from inline chat was accessing properties on the editor object without first checking if it was null. This adds null checks before accessing the document and uri properties to avoid potential null reference errors.
This should fix an issue that I run into where VS Code is complaining about
Cannot read properties of undefined (reading 'scheme')
when I try to start a new chat session:Test plan
I'm not sure what the exact steps to reproduce the issue I run into, but try interacting with Cody without using inline chat, then make changes to your text document and then start a new conversation, you should not see the error message about
Cannot read properties of undefined (reading 'scheme')
: