Fix .values()/get_value_generator()
dealing with Dynamic params and an updated default value
#1058
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.
Fixes #1057
.param.values()
uses.param.get_value_generator()
under the hood (this looks all overly complicated but that's another issue) to obtain the value of a Parameter.get_value_generator()
seems to be designed to deal specifically with Dynamic Parameters (likeInteger
,Number
, etc.), to return the generator callable. So in cases where there's no generator, we simply return the value.