Expand variables in path#80
Draft
antirotor wants to merge 1 commit into
Draft
Conversation
expand `~`, `$VAR` and `{VAR}` in path
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changelog Description
Expand
~,$VARand{VAR}style variables in path.Additional review information
Expansion is applied only in
setResolvedAssetPath(const std::string &)— the overload that receives raw string paths from pinning files, cache misses, and memcached. TheArResolvedPathoverload is left untouched since those paths should already be fully resolved.Note
To be useful with ynput/ayon-core#1884
Testing notes:
Setup variables in roots
Resolve USD assets with the resolver build