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

Support additional data type #215

Open
BFalquet opened this issue Jun 6, 2024 · 3 comments
Open

Support additional data type #215

BFalquet opened this issue Jun 6, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@BFalquet
Copy link

BFalquet commented Jun 6, 2024

Using a column of class difftime as key or disp column in a listing is apparently not supported during export as txt and result in:

number of columns of matrices must match (see arg 2)

Could we consider less cryptic error message in formatters::export_as_txt, a warning in as_listing or just supporting this class ? Several users have come with the same issue.

Cheers

@BFalquet BFalquet added the enhancement New feature or request label Jun 6, 2024
@gmbecker
Copy link
Collaborator

gmbecker commented Jun 6, 2024

The issue is likely that the matrix_form method for listings doesn't understand how to format a difftime column, which begs the question, if they were going to support this, what is the desired behavior and how does it interact with the concept of formats in formatter

@BFalquet
Copy link
Author

BFalquet commented Jun 7, 2024

@gmbecker that is actually a good question, I am not sure what the users actually want. Maybe just a clearer error message would be enough.

@Melkiades
Copy link
Contributor

Using a column of class difftime as key or disp column in a listing is apparently not supported during export as txt and result in:

number of columns of matrices must match (see arg 2)

Could we consider less cryptic error message in formatters::export_as_txt, a warning in as_listing or just supporting this class ? Several users have come with the same issue.

Cheers

We never supported that object in input. I think it was always transformed to character

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

3 participants