Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Relative path for current directory when indicating filepath
See original GitHub issueIs your feature request related to a problem? Please describe. Lack of dot notation “./” when referencing filepaths is kind of annoying.
Describe the solution you’d like I would prefer to be able to use relative filepaths (like “~/myproj/myfile.txt” or “./myproj/myfile.txt”) to indicate the current directory, rather than indicating the full filepath each time.
Describe alternatives you’ve considered You have to use the full filepath to a file or directory or the azure client will throw an error.
Additional context Encountered this issue when running the following command:
az artifacts universal publish --organization $ORG --project="$PROJECT" --scope project --feed $FEED --name initial-package --version $VERSION --description "$DESCRIPTION" --path $SINGLEFILE
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Layer8Err Thanks for getting back. I am doing some research on this. I will get back to you once I have an update on this.
Hi, we’re sending this friendly reminder because we haven’t heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!