fix(debugger): incorrect docs after removal of forge debug
#1477
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
zerosnacks
changed the title
debugger): incorrect docs after breaking regex changes
zerosnacks
changed the title
debugger): incorrect docs after breaking regex changesdebugger): incorrect docs after removal of forge debug
Deploying foundry-book with
|
| Latest commit: |
c8b45c7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://79d56ab5.foundry-book.pages.dev |
| Branch Preview URL: | https://zerosnacks-fix-debugger-docs.foundry-book.pages.dev |
3 tasks
zerosnacks
requested review from
mattsse,
onbjerg,
grandizzy and
yash-atreya
as code owners
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.
Related: foundry-rs/foundry#10079
This doc was previously written for the standalone
debugcommand, now that it is rolled intoforge testandforge scriptthe default of<PATH>is not very helpful in the context of function debugging. Update the doc to point the user to use--match-testto select a single function instead.