unique scenario variables per user type instance #338
Closed
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
… orphan template in all scenarios
boffman
approved these changes
Aug 21, 2024
mgor
force-pushed
the
bug/scenario_variables
branch
4 times, most recently
from
223e87e to
95d9f5d
Compare
mgor
force-pushed
the
bug/scenario_variables
branch
from
95d9f5d to
1587d23
Compare
|
brb |
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.
each instance of a user type must have a unique
Environment._globalsdictionary so they don't interfere with each other when running in the same process.also, background steps that can contain values with templates must add them as orphan templates for all scenarios.