Accept lists as `loggit` input
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
So far, when loggit receives a list as input, the content is distributed across several columns, although most lists could easily be converted into a character vector and also be accepted.
This is particularly important because the previous documentation was/is ambiguous as to which objects are valid input.
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.
Research direction
No files or tests are named. Start by locating the loggit input-handling entry point and the documentation describing valid inputs, then inspect how lists are currently distributed across columns. Done means appropriate lists are accepted as character-vector input and the documentation clearly states which objects are valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100