use ... to specify path in i_am()?

Open
#67 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
tooling

Research direction

Start with the i_am() documentation and compare how its ... argument is handled with here(). Trace the path handling for compound paths and confirm that i_am() accepts them without requiring a file separator; done when the documented behavior is implemented consistently with here().

Written by the indexing model from the issue text.

Description

This may be a picky point, but the only way to use i_am() with a compound path is to provide the file separator. I understand that one of the goals of {here} is to abstract the file separator away from the user.

Could the ... argument in i_am() be implemented the same way as it is for here()?

I see from the i_am() documentation that ... is reserved for future use, could this be it?

Thanks!

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from r-lib/here

All issues in r-lib/here

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.