Don't require dplyr for fortify.tbl()
#5969
Merged
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 aims to fix #4786.
Briefly, it attempts to exploit that some
as.data.frame()
methods will implicitly usecollect()
to realise a local data.frame.For example:
This should ensure that you can still work with e.g.
<tbl_sql>
classes that will becollect()
'ed while not requiring {dplyr} for thefortify.tbl()
method. Example demonstrating we can still use lazy data.frames:Created on 2024-07-02 with reprex v2.1.0