Advanced handling of `loggit` vector inputs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- R
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Vector (and list) inputs (longer than one entry) in loggit() currently lead to a warning and several entries in the log.
Since both JSON and data.frame offer an easy way to save a list or vector per entry, there should be an optional controllable behavior with the options:
-
"warn": The previous multiline behavior including a warning. (Should it remain the default behavior?) -
"multiline": The previous multiline behavior without a warning. (Maybe the new default?) -
"toString": Vectors that contain more than one element are tried to be converted into a single string usingtoString() -
"vector": The elements are all converted usingas.character()and entered as a list in the JSON log
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
Start by reading the loggit() implementation and tracing how vector and list inputs currently produce warnings and multiple log entries. Clarify the default behavior and implement the selected warn, multiline, toString, and vector options, with tests covering each mode and confirming the resulting log representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100