Feature idea - here::right_here()
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the existing i_am() workflow and how here() resolves paths. Define the behavior and API for the proposed right_here() function, including how it uses the file path supplied to i_am(). Done means assets/... resolves relative to that presentation file without repeating its full path, with tests covering the example structure.
Written by the indexing model from the issue text.
Description
Hello!
First of all, thank you for this package. I have been using it for some time, and it is a great tool!:)
I sometimes create multiple presentations within a single RStudio project with their own assets. The file structure looks like this:
ProjectFolder/
├── project.Rproj
└── presentations/
├── presentation01/
│ ├── presentation.qmd
│ └── assets/
└── presentation02/
├── presentation.qmd
└── assets/
If I want to access files from the assets folder, I need to do the following (in each .qmd file)
here::i_am("presentations/presentation01/presentation.qmd")
# Accessing assets
here::here("presentations/presentation01/assets/...")
You might see where I am going with this - I always need to write the initial path to the file. I am proposing a new function called here::right_here() (or any other - any suggestions are welcome!) that would not require the path. The new workflow would then look like this:
here::i_am("presentations/presentation01/presentation.qmd")
# Proposed function
here::right_here("assets/...")
If you feel this function is useful and fits this package, I will gladly help with the implementation:)
What do you think?
- Dominant language
- R
- Stars
- 436
- Forks
- 45
- Avg merge
- 4m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from r-lib/here
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
here v1.0.2 Open
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
beginners blocker
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enviPathR OpenBuild Error Build OK Build Warning policies-accepted pre-review precheck-passed
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Bioconductor/BiocContributions#207 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
datacarpentry/semester-biology#1255 ·