microsoft / microsoft/monaco-editor
[Bug] In peek view 'Go to references' is not navigating to the specific file editor when double click on the specfic references.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.8k
- Forks
- 4.1k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 1
Description
Reproducible in vscode.dev or in VS Code Desktop?
- Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
- Not reproducible in the monaco editor playground
Monaco Editor Playground Link
I our application we are using the monaco editor using angular JS, Go to references is not navigation to the specific editor.
"monaco-editor": "0.41.0", this the version
Monaco Editor Playground Code
Reproduction Steps
No response
Actual (Problematic) Behavior
No response
Expected Behavior
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report concerns Monaco Editor 0.41.0 in an AngularJS application; no repository files, tests, playground code, reproduction steps, or expected behavior are provided. Start by reproducing the peek view's “Go to references” double-click flow in that application and compare it with the stated behavior in VS Code and the Monaco playground. Done means selecting a reference navigates to its specific file editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100