Fixed namespace issue due to roxygenise call #29
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.
Fixes #28
Since
{roxygen2}
7.0.0 (released 2019/11/12)roxygenise
usespkgload::load_all()
by default. This ends up loading up thedevtools_shims
namespace - which includes its own version of the?
function.This means that when you load up
{docstring}
you can use docstring's version of?
but, behind the scenes, it runsroxygenise()
which then loads up thedevtools_shims
namespace. Next time you use?
you're running the one loaded up indevtools_shims
. This is the source of the error found.Adding the
load = "source"
argument in theroxygenise()
call bypasses loading up thedevtools_shims
namespace but still produces the desired behaviour.