Optionally initialize Session['AVALON_HIERARCHY'] #525
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
If the environment variable 'AVALON_HIERARCHY' is present Session['AVALON_HIERARCHY'] will be initialized with that value.
BigRoy
approved these changes
Feb 6, 2020
davidlatwe
reviewed
Feb 6, 2020
davidlatwe
approved these changes
Feb 9, 2020
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.
In this PR the concept of an extra hierarchy for assets was introduced. You can reference this in your file templates with
{hierarchy}. The value is computed when you set the context to a different asset.However if you start your DCC (only relying on Avalon env variables) and you don't switch to another asset,
Session['AVALON_HIERARCHY']doesn't exist. That gives an error when you open the workfiles app and try to save your work (at least in the new combined context/workfiles app.What's changed?
If the environment variable 'AVALON_HIERARCHY' is present Session['AVALON_HIERARCHY'] will be initialized on start up. That way there is no error when saving your work file without switching context to another asset first.