Implement Source Request as for debug adapter protocol standard #945
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kmagiera
approved these changes
Feb 14, 2025
filip131311
deleted the
@Filip131311/ImplementSourceRequestAsForDAPSpecification
branch
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.
This PR implements
SourceRequestin debug adapter, it is not not currently in use but might be necessary in the future, if we ever get generated source on the extension side. For example we now in the inspector tool we now use the information about the source of component usage, but some future features likereact-scanmight require us to use information about component definition source and the only way to achieve that is to analise the component stackTrace, which points to generated location.How Has This Been Tested:
-run
expo-52-eas-run
react-native-78-the change does not break any of the applications