Allow use of default field formatters, even with custom formatting string #13
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.
This PR changes some of the internal behaviors to hopefully make it easier to customize.
There is still a default format, but it is functionally much simpler. Instead, each of the fields get their own formatters, which are implemented as methods on
as.character
. This means thatglue::glue()
will automatically leverage these formatters when building the documentation.This mean a format such as
({type})\cr {description}
will automatically wrap naked types in backticks and respect quotes the same way the default formatter does.If one prefers to work with the raw values, they can always use
({unclass(type)}) unclass(description)
or provide the formatter as a function.