Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced handling of loggit vector inputs #35

Open
4 tasks
MEO265 opened this issue Feb 4, 2024 · 0 comments
Open
4 tasks

Advanced handling of loggit vector inputs #35

MEO265 opened this issue Feb 4, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@MEO265
Copy link
Owner

MEO265 commented Feb 4, 2024

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 using toString()
  • "vector": The elements are all converted using as.character() and entered as a list in the JSON log
@MEO265 MEO265 added the enhancement New feature or request label Feb 4, 2024
@MEO265 MEO265 added this to the 3.0.0 milestone Feb 4, 2024
@MEO265 MEO265 changed the title Advanced handling of vector inputs Advanced handling of loggit vector inputs Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant