✨ Add support for route to test CodeLens#143
Draft
savannahostrowski wants to merge 3 commits intomainfrom
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #142
This PR adds support for route to test code navigation via CodeLens (basically the complementary feature to the existing test to route code navigation). Some additional details:
typefield on the property bag for the existing telemetry event that tracks whether we were able to provide a CodeLens.codeLens.enabledsetting. I've opted to not carve out a separate setting for this as I suspect that users who don't want test to route code nav will probably also not want route to test code nav.findTestClientCallsfromTestToRouteCodeLensProviderintoextractors.tsso it can be shared with the new test index.