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

fix(51223): Go-to-definition for yield and await keyword; jump to respective function definition #51838

Merged
merged 1 commit into from
Dec 20, 2022

Conversation

abuob
Copy link
Contributor

@abuob abuob commented Dec 9, 2022

Fixes #51223

My first PR on this project, apologies in advance in case I missed anything in the guidelines.

Please note that there was some discussion in the issue for await, whether it should jump to the function definition or the respective async. This PR does the former - in the very most cases, they should be right next to each other either way, and the latter seems slightly more involved to implement (which I'm absolutely willing to tackle though if preferred).

Furthermore, in the case of an error (e.g. surrounding function is not async/generator), this implementation should not provide any goToDefinition.

@typescript-bot typescript-bot added the For Backlog Bug PRs that fix a backlog bug label Dec 9, 2022
@abuob
Copy link
Contributor Author

abuob commented Dec 9, 2022

@microsoft-github-policy-service agree

@sandersn sandersn merged commit 8b6f873 into microsoft:main Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
For Backlog Bug PRs that fix a backlog bug
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Go-to-definition on await/yield should probably jump to the containing respective async function/generator
4 participants