-
Notifications
You must be signed in to change notification settings - Fork 6
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
setup_reprex() #245
Comments
We have a naming issue because we have 3 candidate reprex related features :
That's why I named this setup_reprex but it's not a great name either Maybe:
|
The general way to deal with this is tricky, we should capture every argument's expression and environment (the env should be parent.frame() except for dots, we might use The draft PR #100 was trying some clever approaches but it's a can of worms. |
Let's close for now |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
setup_reprex(fun, n = 1, nse = NULL)
This basically traces the function for n calls, it opens a new untitled script every time, and constructs arguments and the call.
This is not the most general way to approach things because NSE and environments are complex, but this should really be ok for 99% use cases I think.
Call without a fun or n arg from inside the function itself to create a reprex while debugging, using locally modified values if relevant
The text was updated successfully, but these errors were encountered: