Pull roxygen2 location from Library#1239
Merged
Merged
Conversation
DavisVaughan
force-pushed
the
feature/static-roxygen2-completions
branch
from
1135abe to
0d43145
Compare
DavisVaughan
force-pushed
the
feature/static-roxygen2-completions
branch
from
5397190 to
4d612d6
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Part of #1095
I'm going to assume that
Libraryholds a good enough.libPaths()for roxygen2 completions purposes, and that it will only get better and more accurate (i.e. more dynamic to users changing.libPaths()) as time goes on