Comments (2)
I'm not working on devtools at the moment, but made a quick visit while clearing notifications.
One high-level observation I have about this issue and #2545 is that it feels like the participants are sort of approaching examples as if they are tests. The tidyverse team maintains a lot (>200) packages and I'm pretty sure none of us make regular usage of run_examples()
. Now that doesn't mean it's a bad function! Rather I think we approach examples differently. When tinkering with them, we execute them interactively. Then, if unexpected problems crop up, we're going to hear about it in CI, i.e. one of our R CMD check
or pkdgown jobs is going to fail.
A lot of the features being requested are available already in the testing side of things and it just feels like the code where you need all of that control sounds more like test code than example code.
from devtools.
@jennybc I have found that I use run_examples()
/ run_example()
a lot when first developing my packages, i.e. when I'm still working out the kinks in new functionality. You're right that it's sort of like testing, but since the examples also need to be debugged at the beginning, having more control over what you run can be very helpful.
Having said that, I do think pkgload::run_example(path, ...)
and pkgload::dev_example(topic, ...)
cover what I need (and allow for the kind of functionality that @pawelru is referring). In #2545, I just hadn't realized those existed (I've since updated that request for clarity).
from devtools.
Related Issues (20)
- Simpler `test_coverage_active_file()` implementation
- Upkeep for devtools (2023)
- Add dev_example() to documentation for run_examples() HOT 3
- `release` causes me a problem if 'foghorn' package is installed HOT 1
- Using system.file in a tryCatch environment HOT 2
- Export is not working when using typed library HOT 3
- Solution to the "checking examples ... ERROR" HOT 1
- Clearly list system dependencies in documentation HOT 1
- `load_all()` documentation refers to `is_loading()`
- devtools::check(error_on="warning") doesn't error on warnings from documenting HOT 4
- `run_examples()` fails if `tests/testthat/helper.R` contains an un-exported function
- Update README reg R Packages second edition
- .
- Can't install the package HOT 2
- can not install devtools in R4.4.1 HOT 4
- do not ask about `check_rhub()` in `release()` because it is deprecated and defunct
- Deprecate `install_*`
- Import pak
- Use `httr` conditionally
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from devtools.