Allow turning off context unrolling for post_generation decorator. #1110
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
m000
force-pushed
the
post-generation-unroll
branch
from
e933211 to
78c2ec3
Compare
m000
force-pushed
the
post-generation-unroll
branch
from
78c2ec3 to
2ecf6b1
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.
In some cases, it is desired to pass lazy functions as post-generation kwargs. E.g. provide a factory.LazyFunction, that will in turn be used as a keyword argument to create_batch().
Because context unrolling is enabled for PostGeneration, this is not possible because the lazy function will be evaluated (unrolled) before calling the post-generation function.
With this PR, it is possible to disable context unrolling for post-generation, depending on the use case.