Uses the fully-qualified module path when getting the module name #78
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.
The existing implementation would use "local" module name when getting the current module. This caused collisions if there were multiple submodules with the same name. This commit uses the "absolute" module name for a given module so that collisions do not occur.
I ran into this problem as I will put unit tests in a
tests
module for every module. The implementation of "cargo run tests-in-this-buffer" was using the "local" version so would run all the tests when I just wanted to run a few of the tests (namely those in the current module).Updating this function to use the fully-qualified name should not break any existing use of this package and provides the functionality I would expect from a function with this name (i.e. run just the tests in this module).