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

Accept lists as loggit input #37

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

Accept lists as loggit input #37

MEO265 opened this issue Feb 4, 2024 · 0 comments
Labels
doc ≠ code Ambiguity as a legacy from before the fork enhancement New feature or request
Milestone

Comments

@MEO265
Copy link
Owner

MEO265 commented Feb 4, 2024

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.

@MEO265 MEO265 added bug Something isn't working enhancement New feature or request labels Feb 4, 2024
@MEO265 MEO265 added this to the 3.0.0 milestone Feb 4, 2024
@MEO265 MEO265 added doc ≠ code Ambiguity as a legacy from before the fork and removed bug Something isn't working labels Feb 4, 2024
@MEO265 MEO265 changed the title Accept lists as input Accept lists as loggit input Feb 4, 2024
@MEO265 MEO265 modified the milestones: 3.0.0, 2.3.0 May 4, 2024
@MEO265 MEO265 modified the milestones: 3.0.0, 2.3.0 May 14, 2024
@MEO265 MEO265 modified the milestones: 2.3.0, 3.0.0 Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc ≠ code Ambiguity as a legacy from before the fork enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant