[NFC] Refactor the package_relpath function to make it easier for other packages to use it
#60
Conversation
This file contains 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
…ther packages to use it
DilumAluthge
force-pushed
the
dpa/refactor_package_relpath
branch
from
bd8243c
to
04d60dc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'd like to use the
RegistryTools.package_relpathfunction in other packages (e.g. RegistryCI) in which I have the package name (as aString), but I don't necessarily have aPkg.Types.Project.This PR refactors the
RegistryTools.package_relpathfunction and adds a method that takes in the package name as a string.This PR has no functional change.