fix: added replay debugging to ApexLibraryExecuteExecutor #3758
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
|
@rcoringrato-sfdc , traceFlags.ts is in |
|
@jeffb-sfdc I missed that initially, that would be a good move. |
jag-j
approved these changes
Jan 19, 2022
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.
What does this PR do?
This PR adds Apex debug replay to when anonymous Apex is executed.
What issues does this PR fix or reference?
@W-10288326@
Functionality Before
When the execute anonymous command was invoked, it would run but the flow was execution only.
Functionality After
Now, when the execute anonymous command is invoked, the anonymous Apex runs, and then the replay debugger runs.