Update kable to allow custom formating #1827
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
With the latest addition, I added a test to confirm custom formatting of non-numeric vectors works. |
3 tasks
|
Thanks @yihui! I found this while working on {colortable} and playing around with vctrs. Hoping this will resolve this for everyone! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the coming of vctrs, it is probably inevitable that there will be a number of new vector classes. And with that, a number of custom printing methods. With the current format of kable, it uses
as.matrix()to handle the conversion, but it might be better to handle the conversion explicitly.As far as I could test, this would not change the general behavior.