Update docs#4
Conversation
…e contributing guidelines, and enhance README files
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d02ee3138f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const showGraphCmd = vscode.commands.registerCommand( | ||
| 'referenceGraph.show', | ||
| (uri?: vscode.Uri) => webviewProvider.showReferenceGraph(uri) | ||
| (uri?: vscode.Uri) => webviewProvider.showReferenceGraph() |
There was a problem hiding this comment.
The command handler now ignores the URI that VS Code passes when the command is triggered from the Explorer context menu, so right‑clicking a file and choosing “Show Reference Graph” will instead operate on the active editor (or show the “No active editor” warning) rather than the selected file. This is a regression for the Explorer menu contributed in package.json (explorer/context uses referenceGraph.show), and it effectively removes the ability to build a file reference graph for a file that isn’t open. Consider forwarding the uri to showReferenceGraph (or restoring a separate file-reference command) so the Explorer entry still targets the selected file.
Useful? React with 👍 / 👎.
1 participant
No description provided.